Expand AI logo
DocsDocs
Glow Active
API Reference
Login

Documentation

Get Started

OverviewWhy ExpandQuickstartWays to Use Expand

Agent Quickstarts

OverviewExpand SkillClaude CodeCursorCodexOpenCodeSkill-Based AgentsOther MCP Clients

Fetch

OverviewHow Fetch WorksOutput ModelInclude OptionsBrowser BehaviorHighlightsPlayground & ReplayBatched Fetch

Reference

API ReferenceCLI CommandsMCP Tools & ResourcesTypeScript SDKPython SDK

Account & Billing

Pricing & UsageTiersFAQ

Machine-Readable Docs

start.mdllms.txtllms-full.txtDocs as Markdown
Browse docs

Get Started

OverviewWhy ExpandQuickstartWays to Use Expand

Agent Quickstarts

OverviewExpand SkillClaude CodeCursorCodexOpenCodeSkill-Based AgentsOther MCP Clients

Fetch

OverviewHow Fetch WorksOutput ModelInclude OptionsBrowser BehaviorHighlightsPlayground & ReplayBatched Fetch

Reference

API ReferenceCLI CommandsMCP Tools & ResourcesTypeScript SDKPython SDK

Account & Billing

Pricing & UsageTiersFAQ

Machine-Readable Docs

start.mdllms.txtllms-full.txtDocs as Markdown

llms.txt

A compact curated docs entrypoint for agents.

Root llms.txt gives agents a compact entrypoint into Expand docs: setup first, then docs, API Reference, and the full docs bundle.

https://expand.ai/llms.txt

llms.txt is for agents and tools you explicitly point at Expand's docs. Do not treat it as a guarantee that major AI search engines crawl or rank the site differently. Its practical value is as a handoff URL for coding agents, IDE assistants, and MCP tools.

Open llms.txt

Curated root entrypoint.

Docs index

Generated authored-docs table of contents.

Full docs bundle

Full authored docs as Markdown.

Which file should I use?

URLUse whenSource
https://expand.ai/llms.txtAn agent needs first orientation.Curated root route.
https://expand.ai/docs/llms.txtAn agent needs the authored docs table of contents.Generated from authored docs pages.
https://expand.ai/docs/llms-full.txt

Root llms.txt is curated. /docs/llms.txt is generated. /docs/llms-full.txt is the full authored-docs bundle.

Recommended root shape

Root llms.txt follows the llms.txt convention: an H1, a one-line blockquote summary, short guidance, then H2 sections of Markdown link lists with concise descriptions. Setup links come before general docs, and ## Optional holds links an agent can skip when context is tight.

# Expand

> Expand Fetch turns live web pages into agent-ready Markdown, State JSON, evidence, and replayable snapshots.

Use `start.md` when setting up an agent. Use `llms-full.txt` when you need the full authored docs bundle. Use API Reference Markdown routes for exact endpoint schemas.

## Start Here

- [Agent setup guide](https://expand.ai/start.md): Set up Expand across every detected coding agent.
- [Docs](https://expand.ai/docs): Human-authored docs.
-

The root file stays curated and small. It should include:

  • the project name and short summary;
  • the start guide link;
  • the human docs link;
  • the API Reference link;
  • the full authored docs bundle link;
  • the canonical agent setup prompt;
  • optional links for secondary machine-readable resources.

It should not become the full docs dump. Where a Markdown-readable target exists, link the .md or .mdx route instead of the HTML page so agents read Markdown directly.

What /docs/llms.txt includes

/docs/llms.txt is a generated index of authored docs pages. It should list page titles, links, and short descriptions.

  • It is generated from the authored docs source, not hand-written.
  • Use it when an agent needs a docs table of contents.
  • Page links should prefer Markdown-readable targets such as .md or .mdx routes.
  • It does not replace root /llms.txt for setup and routing.
  • It does not include generated API Reference pages. For endpoint schemas, use /api-reference and its Markdown export routes.

What /docs/llms-full.txt includes

/docs/llms-full.txt is a larger authored-docs bundle. Use it when the agent has enough context budget and needs the docs content, not just the index.

  • It is generated from processed Markdown for authored docs pages.
  • Each page section includes a title and canonical source URL before the page body.
  • Pages are separated within the bundle.
  • It is not the same as the API Reference Markdown export.
  • It can be too large for some prompts. For a single topic, append .md to the docs URL instead.

Related machine-readable docs

ResourcePurpose
start.mdAgent setup guide and setup prompt.
llms.txtCompact curated agent entrypoint.
llms-full.txtFull authored-docs bundle.
Docs .md / routes

Related pages

  • llms-full.txt
  • start.md
  • Docs as Markdown
  • API Reference
Previousstart.md
Nextllms-full.txt

On This Page

Which file should I use?Recommended root shapeWhat /docs/llms.txt includesWhat /docs/llms-full.txt includesRelated machine-readable docsRelated pages
An agent needs the full authored docs bundle.
Generated from processed authored docs Markdown.
[
API Reference
]
(https://expand.ai/api-reference)
: Exact endpoint schemas and errors.
- [Full docs bundle](https://expand.ai/docs/llms-full.txt): Full authored docs as Markdown.
## Recommended Paths
- [Quickstart](https://expand.ai/docs/get-started/quickstart.mdx): Run the first Fetch.
- [Ways to Use Expand](https://expand.ai/docs/get-started/ways-to-use-expand.mdx): Choose agents, CLI, SDKs, API, or Playground.
- [Fetch Overview](https://expand.ai/docs/fetch/overview.mdx): Understand the Fetch product.
## Agent Setup Prompt
Read https://expand.ai/start.md and set up Expand.
## Optional
- [Docs index](https://expand.ai/docs/llms.txt): Compact authored-docs index.
.mdx
One authored docs page as Markdown.
API Reference Markdown routesExact endpoint docs and schemas as Markdown.