llms-full.txt

What it contains

/docs/llms-full.txt is generated from authored docs pages. It is not the same as the API Reference Markdown export.

The bundle is assembled from the authored docs source and contains:

• processed Markdown for authored docs pages;
• one chunk per authored docs page;
• the page title before each page body;
• the canonical source URL before each page body;
• separators between page chunks;
• no generated API Reference pages unless the implementation intentionally changes.

Each chunk uses the processed Markdown, not the raw .mdx source, so the agent reads the same rendered content a human sees.

Output shape

Pages are concatenated in docs order. Each chunk opens with a heading that carries the page title and its canonical URL, then the page body, then a --- separator before the next page.

Each page chunk must preserve a title and canonical source URL so agents can cite or revisit the source page.

What it does not contain

• It is not the root orientation file.
• It is not the generated API Reference bundle.
• It is not a replacement for exact endpoint schemas.
• It is not a setup guide by itself.
• It may be too large for small context windows.

Use API Reference Markdown routes when the agent needs exact endpoint schemas, parameters, errors, or generated examples.

When to use it

Use /docs/llms-full.txt when:

• the agent needs broad authored-docs context;
• the agent has enough context budget for a large bundle;
• docs search is not available;
• a single full-docs pull is simpler than fetching pages one by one.

Avoid /docs/llms-full.txt when:

• the agent only needs setup — use /start.md;
• the agent only needs orientation — use /llms.txt;
• the agent only needs the docs table of contents — use /docs/llms.txt;
• the agent needs one page — use that page's .md route;
• the agent needs exact endpoint schemas — use API Reference Markdown routes.

Relationship to API Reference

API Reference is separate from authored docs. /docs/llms-full.txt should not be assumed to contain generated endpoint schemas.

Authored docs explain how to use Expand. The generated API Reference owns exact endpoint schemas, request bodies, response models, and status codes. When the agent needs that level of precision, reach for an API Reference Markdown route instead of the bundle:

• /api-reference.md;
• /api-reference.mdx;
• nested /api-reference/...md;
• nested /api-reference/...mdx;
• a request to any API Reference page with Accept: text/markdown.

These schemas live only in the API Reference routes; they are not duplicated in /docs/llms-full.txt.

Generation and maintenance

The bundle is regenerated from the authored docs source, so it stays in sync as pages change. When updating it, keep these invariants:

• generate from the authored docs source, not a hand-maintained list;
• emit processed Markdown, not raw MDX source;
• preserve stable page ordering;
• preserve the title and canonical URL for every page chunk;
• use a consistent separator between pages;
• confirm whether API Reference stays excluded — if it is ever included, measure the output size and update this page's copy.

Tests for the route should assert the content type, that Accept: text/markdown requests resolve correctly, that each chunk carries a title and canonical URL, that the separator is present, that at least one known authored page appears, that processed Markdown is non-empty for included pages, and that ordering stays stable after IA changes.

Related pages

• llms.txt
• Docs as Markdown
• start.md
• API Reference