Independent docs benchmark desk

Before an agent touches your docs, check the benchmark.

This public documentation benchmark tests whether an agent can discover the right page, fetch readable text, follow the instructions, and recover when the docs get fuzzy.

Use it as a public docs leaderboard, a fast AI-readability audit, or a way to compare API docs, developer docs, and help centers before a prospect or agent does.

Human Machine

Leaderboard

Search benchmark reports and open the full breakdown.

Compare public docs across categories, inspect the strongest performers, and jump into the detailed report for any site.

Search leaderboard242 docs

Categories7 tracked segments

Showing 1-25 of 242 matching docs.

#DocsCategoryChecksWarningsFailedScore

docs.eco.com

16/17passed

102Excellent

docs.cdp.coinbase.com

docs.cdp.coinbase.com

DocsAlot runs

16/17passed

0warnings

1failure

100Excellent

Snowflake

20/22passed

100A+

Promptless

promptless.ai

20/22passed

1warning

0failures

100A+

Alchemy

20/23passed

100A+

Bolt

18/22passed

ID.me

20/23passed

Introduction

18/22passed

Backboard

18/18passed

Feather

18/22passed

Runpod

19/22passed

Merge

21/23passed

Nvidia Dynamo

docs.nvidia.com/dynamo

18/23passed

Fern

buildwithfern.com/learn

21/23passed

kitaru-site-preview-303.zenml-migration.workers.dev/docs

kitaru-site-preview-303.zenml-migration.workers.dev/docs

15/17passed

maesn

16/22passed

Contentsquare

docs.contentsquare.com

18/22passed

Brevo

20/23passed

Nvidia

docs.nvidia.com/heavyai

17/23passed

Skyflow

16/22passed

developers.expanse.host

developers.expanse.host

15/17passed

Shipfox

17/22passed

Postman

16/22passed

Circle

developers.circle.com

15/22passed

Novu

16/22passed

Why it matters

Docs quality now affects AI usability.

This is not a vanity score. It is a practical read on whether an agent can discover, read, and act on your documentation.

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 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

Read the open standard for agent-friendly documentation.

GitHub repo

agent-ecosystem/afdocs

Inspect the source and contribute to the spec directly.

Author

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 fixes the layer this benchmark exposes: docs structure, AI-readable outputs, developer onboarding, and the workflows that keep help centers and API docs current.

Fix your docs with DocsAlot Book AI visibility audit

Resources

Learn how to improve a docs benchmark score.

These pages help teams move from a benchmark report to concrete improvements in docs structure, AI discoverability, and developer onboarding.

Benchmark hub

Browse the full benchmarks hub

See how docs benchmark pages fit into the wider benchmark roadmap for CLI, MCP, and API workflows.

Free tool

Run DocsAgent Score on one docs site

Use the single-site audit when you want a quick docs benchmark before opening the full leaderboard.

Category page

See what AI-readable documentation requires

Use the category page when you want the operational checklist behind better benchmark scores.

Workflow

Review the API docs automation workflow

See how docs, SDKs, CLIs, and agent-facing outputs can ship from one OpenAPI-driven system.

Workflow

See the OpenAPI to CLI generator page

Look at the CLI and SDK workflow if the benchmark gaps are really onboarding and implementation gaps.