What already works.
- Page Size and Truncation Risk is relatively strong at 100/100.
- URL Stability and Redirects is relatively strong at 100/100.
- Authentication and Access is relatively strong at 100/100.
Gamma scored 91/100 on Fern's public Agent Score report across 22 published checks. This developer docs benchmark shows where agents can use these docs cleanly and where the biggest points of friction still are.
This report passes 16 of 22 checks, with 1 warnings, 2 failed checks, and 3 skipped checks still shaping the next score lift.
Start with what already works, then move to the fixes most likely to lift the score.
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 10 pages under 50K chars (median 7K, max 25K)
All 10 sampled pages convert under 50K chars (median 7K, 0% boilerplate)
Content starts within first 10% on all 10 sampled pages (median 0%)
Can an agent tell whether the docs are fresh and trustworthy?
llms.txt covers 96% of 24 sitemap doc pages; 1 llms.txt links not in sitemap (may indicate stale links or incomplete sitemap)
4 of 10 pages have substantive content differences between markdown and HTML (avg 17% missing)
All 12 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 49 code fences properly closed across 12 pages
Can an agent fetch a clean text version of the docs?
10/10 sampled pages support .md URLs (100%)
10/10 sampled pages support content negotiation (100%)
Can an agent find the right starting point?
llms.txt found at 2 location(s)
llms.txt contains parseable links but doesn't fully follow the proposed structure: https://developers.gamma.app/llms.txt: No blockquote summary found; https://developers.gamma.app/docs/llms.txt: No blockquote summary found
llms.txt is 3,354 characters (under 50,000 threshold)
No HTTP(S) links found in llms.txt
No HTTP(S) links found in llms.txt
No llms.txt directive found in any of 10 sampled pages
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.
99/100 score in Productivity. Open the full documentation benchmark report.
92/100 score in Productivity. Open the full documentation benchmark report.
91/100 score in Productivity. 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.
Use this guide when you want to improve the same categories this benchmark scores.
One of the fastest ways to improve docs discoverability for agents.
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.