/ llmtxt.info
Français

Real-world llms.txt examples

A curated gallery of /llms.txt files in production. Useful for inspiration — and for spotting patterns worth copying.

Last updated:

All links go to the source files on the original sites. Snapshot dates indicate the last time we manually verified the file existed and matched the description.

Vercel

Platform

Vercel exposes /llms.txt at the marketing root with sections for product surfaces and key documentation entry points.

Demonstrates llms.txt usage on a marketing site (not just docs).

Stripe

Documentation

Stripe's documentation exposes /llms.txt with sections grouped by API surface (Payments, Connect, Billing, Identity, Issuing).

Strong example for large API documentation. Each section points to a focused subset of pages.

Perplexity

Documentation

Perplexity's API docs publish a compact /llms.txt that maps each endpoint to its dedicated reference page.

Good example of an API-first /llms.txt — short, focused, easy to parse.

Mintlify

Platform

Mintlify auto-generates /llms.txt and /llms-full.txt for every documentation site hosted on their platform.

Mintlify co-developed the llms-full.txt convention with Anthropic.

Cloudflare

Documentation

Cloudflare's developer docs site exposes /llms.txt with sections grouped by product (Workers, R2, D1, Pages, Zero Trust, etc.).

Per-product /llms-full.txt variants are also published under each product's docs root.

Anthropic

Documentation

Anthropic's developer documentation publishes both /llms.txt and /llms-full.txt, organized by product surface (API, Claude Code, Agent SDK).

One of the cleanest reference implementations. Sections are stable and well-named.

Patterns to copy

  1. Group by product surface, not by content type. Stripe, Cloudflare and Anthropic all section by product (Payments, Workers, Claude API), not by “blog / docs / guides.” That matches how an LLM client usually queries.
  2. One sentence per item, factual. Avoid marketing language. The note after the colon is for disambiguation, not for selling.
  3. Keep the root file small. If you have many products, publish per-product variants (e.g. /workers/llms-full.txt) instead of one giant root file.
  4. Pair with llms-full.txt. Most documentation adopters publish both. The map is for navigation, the full file is for ingestion.
  5. Use absolute URLs. Every example we list does this. Relative URLs make the file ambiguous when copied around.

Submit an example

Want your llms.txt listed? Open a pull request on the project repository with a new entry under src/content/examples/. The only requirements are:

  • The file is publicly accessible at the listed URL.
  • It validates against our validator with no errors.
  • You can describe it in two sentences without marketing language.