Well-known llms aliases for agent compatibility
Serve `/.well-known/llms.txt` and `/.well-known/llms-full.txt` alongside the root files so agents that follow the well-known convention can discover your corpus without guessing.
Why this can grow a startup
Agent clients do not all start from the same place. Some check the site root. Others look for a well-known path first. Shipping both removes an avoidable discovery failure and makes the machine-readable layer more durable if your docs stack or proxy setup changes later.
Company example
Mintlify hosts `llms.txt` and `llms-full.txt` at both the site root and the `/.well-known/` paths for compatibility with tools that follow the well-known convention.
Source and metric
Source: Mintlify Docs · Browse Mintlify Docs tactics
Mintlify serves both llms files at the root and at `/.well-known/` compatibility paths
Source discovered: May 27, 2026
When to use it
Use this when SEO, AI Search, Website is relevant to ai discovery, crawlability, technical seo and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read Mintlify Docs and identify what is directly supported.
- Choose one channel context: SEO, AI Search, Website.
- Define the test around Mintlify serves both llms files at the root and at `/.well-known/` compatibility paths.
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.