Source directory
849 websites
Active public directory count at time of reference.
Examples
A list of live llms.txt examples.
Use this as a fast comparison view. The active source directory currently tracks hundreds of websites publishing llms.txt files, and the list below highlights a useful cross-section.
Snapshot
Real examples you can open right now.
Source basis: directory.llmstxt.cloud. The public directory showed 849 websites on May 23, 2026. This page pulls out a cleaner list for reference.
What to compare
Summary, links, scope
Look at how sites describe themselves, which URLs they prioritize, and whether they publish llms-full.txt.
| Site | Type | llms.txt |
llms-full.txt |
Pattern | Last checked | Notes |
|---|---|---|---|---|---|---|
| llmstxt.org | Reference spec | 160 tokens | No | Concise root-only | 2026-05-24 | Compact baseline example. |
| Anthropic Claude | Model product | 892 tokens | No | Product summary | 2026-05-24 | Short consumer-facing implementation. |
| Perplexity Docs | Developer docs | 4K | 177K | Root + full pair | 2026-05-24 | Good docs plus full-file pairing. |
| Cloudflare Docs | Developer docs | 49K | 11M | Massive docs hub | 2026-05-24 | Large multi-product documentation system. |
| Vercel AI SDK | SDK docs | 293K | No | Dense reference docs | 2026-05-24 | High-volume reference for API docs. |
| Cursor | Product site | 2K | No | Compact product file | 2026-05-24 | Short and focused. |
| ElevenLabs | AI platform | 22K | No | Broader product map | 2026-05-24 | Broader product surface area. |
| Coinbase CDP Docs | Developer docs | 74K | 2M | Docs-first routing | 2026-05-24 | Good example of canonical docs routing. |
| Model Context Protocol | Open standard | 2K | 235K | Standard + full pair | 2026-05-24 | Useful standard-oriented example. |
| Mintlify | Docs platform | 5K | 184K | Vendor docs pair | 2026-05-24 | Clear docs vendor implementation. |
| Svelte | Framework docs | 349 tokens | 279K | Tiny root + full | 2026-05-24 | Very concise top-level file. |
| Zapier Docs | Integration docs | 14K | 301K | Workflow docs pair | 2026-05-24 | Workflow-heavy docs example. |
| Pinecone Docs | Vector database docs | 12K | 703K | Developer docs pair | 2026-05-24 | Developer documentation structure. |
| Trigger.dev | Developer tool | 8K | 276K | Balanced pair | 2026-05-24 | Balanced top-level and full-file setup. |
| Resend | Email API | 8K | 306K | Product + docs pair | 2026-05-24 | Strong developer-product example. |
| Langfuse | Observability | 3K | No | Compact product file | 2026-05-24 | Simple file, direct use case. |
| CrewAI Docs | Agent framework docs | 9K | 412K | Agent docs pair | 2026-05-24 | Agent-focused docs reference. |
| Tinybird | Data platform | 8K | 319K | Data product pair | 2026-05-24 | Good for data product structure. |
| ProjectDiscovery Docs | Security tooling docs | 8K | 232K | Security docs pair | 2026-05-24 | Dense developer docs example. |
| Infisical | Secrets management | 54K | No | Large root-only | 2026-05-24 | Larger root file without a public full variant. |
What to notice
Patterns worth copying.
Use factual one-line descriptions instead of vague marketing language.
Link to pages that can actually support your claims: product, docs, pricing, support, security, and contact.
Keep the root file scoped. If your site is huge, a concise llms.txt plus an optional llms-full.txt is a common pattern.
Apply it here
Build your draft.
Generate a file in the builder.
Publish it cleanly.
Use the platform guide to get it live at the site root.
Audit the quality.
Read the checklist post before you call it done.
FAQ
Directory questions.
Use the list to compare structure and scope, not to copy another team’s file blindly.
What is this directory for?
It is a comparison view of real websites publishing llms.txt, so you can study how different teams describe their sites and prioritize canonical pages.
Should I copy another site’s file directly?
No. Use the directory to compare structure and scope, then write a file that matches your own products, pages, and claims.
What should I compare when reviewing examples?
Look at the plain-English summary, the priority links, the scope of the file, and whether the site also publishes an llms-full.txt variant.
Why do some sites publish both llms.txt and llms-full.txt?
A concise root file can route agents quickly, while a full variant can provide broader coverage for large docs systems or product surfaces.