Feather scored 98/100 on the DocsAlot benchmark report across 22 published checks. This Documentation benchmark shows where agents can use these docs cleanly and where the biggest points of friction still are.
This report passes 18 of 22 checks, with 2 warnings, 1 failed checks, and 1 skipped checks still shaping the next score lift.
Documentation quality now affects implementation speed, support load, and whether an agent or buyer can stay self-serve. This benchmark shows where the docs already work well and where they still introduce friction.
Good documentation is discoverable, readable in plain text, clear about structure and instructions, and specific enough in examples and next steps that real workflows can keep moving.
These are the clearest signals behind the current score. Start with the strengths that already support discovery and implementation, then use the gaps below to prioritize the fixes most likely to improve AI readability and self-serve onboarding.
For the broader pattern behind these wins, review AI-readable documentation and compare this page with the full docs benchmark leaderboard.
If you want to improve the system behind these gaps, start with API docs automation, the OpenAPI to CLI generator, and this guide to making docs AI-readable.
Open each category to review the checks behind the score and see exactly where agents still hit friction.
Can an agent read the page without losing important context?
All 10 sampled pages contain server-rendered content
All 9 pages under 50K chars (median 5K, max 7K)
1 of 10 sampled pages convert to over 100K chars (max 1513K, 0% boilerplate)
Content starts within first 10% on all 10 sampled pages (median 1%)
Can an agent tell whether the docs are fresh and trustworthy?
llms.txt covers 100% of 167 sitemap doc pages; 1 llms.txt links not in sitemap (may indicate stale links or incomplete sitemap)
All 9 pages have equivalent markdown and HTML content (avg 0% missing)
All 11 endpoints have appropriate cache headers
Can an agent trust that URLs will stay predictable?
All 10 sampled pages return proper error codes for bad URLs
No redirects detected across 10 sampled pages
Can an agent access the docs without getting blocked?
All 10 sampled pages are publicly accessible
All docs pages are publicly accessible; no alternative access paths needed
Can an agent understand how the page is organized?
No tabbed content detected across 10 sampled pages
No tabbed content found; header quality check not applicable
All 10 code fences properly closed across 10 pages
Can an agent fetch a clean text version of the docs?
9/9 sampled pages support .md URLs (100%)
9/9 sampled pages support content negotiation (100%)
Can an agent find the right starting point?
llms.txt found at 1 location(s)
llms.txt contains parseable links but doesn't fully follow the proposed structure: https://docs.featherhq.com/llms.txt: No blockquote summary found
llms.txt is 25,463 characters (under 50,000 threshold)
All 10 same-origin sampled links resolve (169 total links)
10/10 same-origin sampled links point to markdown content (100%) (1 external link excluded)
llms.txt directive found in 9 of 10 sampled pages (1 missing)
Save the report to a work email now, or tell us what kind of ongoing monitoring would be useful for this docs site.
Compare related benchmark reports, then move into the guides and tools that improve documentation benchmark scores.
100/100 score in Other. Open the full documentation benchmark report.
100/100 score in Other. Open the full documentation benchmark report.
99/100 score in Other. Open the full documentation benchmark report.
Compare this documentation benchmark report with other public docs benchmark results.
Score your own API docs or developer docs and open the full public report.
See how docs, SDKs, CLIs, and agent-facing outputs can ship from one OpenAPI-driven system.
Use the CLI page when the benchmark gaps are really onboarding and implementation gaps.
Use this guide when you want to improve the same categories this benchmark scores.
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.