Agents already use docs as product instructions
Coding agents, AI search products, and automated support flows read docs long before a human asks for help. If the docs are hard to fetch or parse, the product feels harder to use.
Docs benchmark
Can agents use your docs?
Run the benchmark on any public docs site and see whether an agent can find the right page, read clean text, and follow the instructions without guesswork.
Try one of these public docs URLs:
We run the crawl here first, then open the full report with scores, failed checks, and next fixes.
Leaderboard
The docs benchmark leaderboard.
Browse public benchmark reports, compare category scores, and open the full breakdown for each docs site.
Rows shown
Showing 25 of 171 matching docs.
#DocsCategoryScoreChecksWarningsFailed
01
Agoradocs.agora.io
Other100A+
20/220002Snowflakedocs.snowflake.com
Other100A+
20/221003Promptlesspromptless.ai
AI100A+
20/221004Alchemywww.alchemy.com/docs
Other100A+
20/232005Boltsupport.bolt.new
Productivity99A
18/222106ID.medocs.id.me
Other99A
20/231107Introductionapi-docs.ollang.com
Other99A
18/222008Backboarddocs.backboard.io
AI98A+
18/180009Featherdocs.featherhq.com
Other98A
18/222110Runpoddocs.runpod.io
Infrastructure98A
19/221111Mergedocs.merge.dev
Other98A
21/230112Nvidia Dynamodocs.nvidia.com/dynamo
Infrastructure98A
18/233013Fernbuildwithfern.com/learn
DevTools98A
21/230114kitaru-site-preview-303.zenml-migration.workers.dev/docskitaru-site-preview-303.zenml-migration.workers.dev/docs
DocsAlot runs97Excellent
15/170215maesndocs.maesn.com
AI97A
16/221416Contentsquaredocs.contentsquare.com
Other97A
18/223017Brevodevelopers.brevo.com
Other97A
20/231118Nvidiadocs.nvidia.com/heavyai
Infrastructure97A
17/233119Skyflowdocs.skyflow.com
Infrastructure97A
16/222220Shipfoxdocs.shipfox.io
Other96A
17/222121Postmanlearning.postman.com
DevTools96A
16/222222Circledevelopers.circle.com
Payments95A
15/220523Novudocs.novu.co
Other95A
16/221124Provedeveloper.prove.com
Other95A
15/235125LaunchDarklylaunchdarkly.com/docs/home
DevTools95A
17/2222Why it matters
Docs quality now affects AI usability.
This is not a vanity score. It measures whether an agent can discover, read, and act on your documentation.
Docs quality now affects activation
Agent-readable docs shape implementation speed, support load, and whether a product feels trustworthy during evaluation.
Benchmarks make docs quality comparable
A shared benchmark gives teams a concrete way to compare docs quality, spot weak areas, and track improvements over time.
Methodology
How the benchmark scores docs.
This scoring model is informed by AFDocs and adapted into a public benchmark teams can inspect, compare, and rerun.
Specification
AFDocs
GitHub repoRead the open standard for agent-friendly documentation.
agent-ecosystem/afdocs
AuthorInspect the source and contribute to the spec directly.
Dachary Carey
Follow the work and background behind the AFDocs effort.
Checks for llms.txt, sitemaps, and a clear public docs entry point.
- LLMS TXT existsAn llms.txt file is published at a predictable docs path.
- LLMS TXT is structuredThe llms.txt file follows a format agents can parse quickly.
- Docs entry point is obviousThe primary docs home is easy to identify.
- Docs sitemap existsThe crawl map is present and reachable.
- Key docs links resolveThe sampled entry links resolve without dead ends.
- Public indexing path is stableAgents can stay on a stable public path while crawling the docs.
Built by DocsAlot
Need help improving the score?
DocsAlot helps teams improve help centers, developer docs, API docs, and CLI docs so they are easier for humans to use and easier for agents to read.