Making your docs site agent-readable: llms.txt, MCP, and the .well-known files that actually matter
AI agents increasingly read your docs instead of a human. If your documentation site only emits HTML for a browser, an agent has to scrape and guess. There's a better surface — and most of it is a handful of small, standard files. Here's the full stack we ship on the OrchestKit docs site, why each piece exists, and how to verify it. 1. llms.txt — the agent's table of contents A plain-text index at /llms.txt: what the product is, its constraints, and a link map to every machine-readab...
Original Source
Read the full article at Dev →KhanList aggregates and links to publicly available news content. We do not host full articles from third-party sources. Always verify important information with original sources.