Kyan Yang
Technical Writing
Share this article
Kyan Yang
Technical Writing
Share this article

Mintlify Index aggregates the docs of over 5000 Mintlify-powered documentation sites into a natural language retrieval layer for coding agents.
The architecture begins by filtering agent queries into two categories:
- Queries that reference docs in the Mintlify-powered ecosystem, which then undergo an internally optimized retrieval process.
- All other queries, which are routed to a standard external provider.
Developer gives an agent an implementation task
↓
Agent calls search or context
↓
Mintlify Index routes each query
├─ product in Mintlify's hosted corpus → all public Mintlify-powered docs
└─ other query → web search
↓
Index returns ranked sources or token-budgeted context
↓
Agent can call contents to inspect a selected source
↓
Agent uses the evidence to answer or plan the change
Each search or context request routes the query to a retrieval source. Queries about products in Mintlify’s hosted corpus use eligible public documentation when those docs are likely to answer the request. Other queries route to a leading third party web search tool. If the selected source fails or returns no results, Index will also fall back to the other.
An agent can retrieve evidence in two ways. context returns an assembled, token-budgeted bundle of ranked excerpts and source URLs. For more control, search returns ranked source metadata and optional matching text. The agent can then pass a Mintlify URL or document ID to contents to retrieve the selected page. With a follow-up query and length limit, contents can return the most relevant section. Index supplies the evidence, afterwhich the agent remains responsible for producing and validating the answer or implementation.
We then ran an experiment comparing Mintlify Index with Context7, a popular docs-retrieval service for coding agents. Across 150 implementation-planning tasks on 50 products hosted on Mintlify, a blinded pairwise judge preferred the plans produced with Mintlify Index in 96 tasks, nearly two-thirds.
Not only did the Mintlify Index group produce higher-quality results, but they also completed tasks 48% faster end-to-end, with 10% higher factual correctness, 10% better citation support, and 17% fewer critical errors.
![]()
In pursuit of our mission to optimize the interaction between agents and knowledge, this experiment showed us the potential benefits of a customized retrieval system only made possible by the ecosystem of Mintlify docs.
We’re launching a beta version of Mintlify Index today, and will use what we learn to continually optimize the affordability, accuracy, and speed.
This is only the beginning.
More blog posts to read

The state of docs traffic: a 2026 midyear report
Agents now account for 66% of measured web-traffic across docs powered by Mintlify, with July logging over 213 million agent web requests and 105 million human page loads as the month comes to a close.
July 29, 2026Kyan Yang
Technical Writing

Docs URL Benchmark: Markdown & llms.txt > HTML
We benchmarked four ways to serve documentation to AI agents (HTML, plain markdown, markdown linking to llms.txt, and markdown with llms.txt inlined) across 2,400 runs on 20 Mintlify docs sites, and found that a single link to llms.txt eliminates most agent 404s at no added cost.
July 17, 2026Aadit Shah
Engineering