Documentation.AI

Last scanned documentation.aiDocumentation.AI15 pages tested

AI agents can find, read and use these docs well. Documentation.AI scores 90 out of 100 (grade A), passing 17 of 27 checks. 9 still need work. 1 could not be verified.

This covers the whole site. The documentation seems to live at documentation.ai/docs: scan it for a docs-only score.

Fix it with Documentation.AI

Get this report by email

We send the full report to your inbox. Nothing on this page needs an email.

Use your work email. We only send what you asked for, and every email has an unsubscribe link.

Developer docs

Kind of site

17/27

Checks passed

7

Partly passed

2

Failed

Access

Content discoverability4 passed1 failed1 partly1 unverified
  • llms.txt links point to Markdown

    Same-origin links point to HTML and no markdown alternatives detected (1 external link excluded)

    Your llms.txt links point to HTML pages. Update them to .md URL variants so agents receive markdown instead of converted HTML.

    Check your fix: Links in llms.txt point at .md URLs, or URLs that return text/markdown.

  • Pages point agents to llms.txt

    llms.txt directive found in HTML of 11 of 15 sampled pages (4 missing)

    An llms.txt directive was found in the HTML of some pages but is missing from others, or is buried deep in the page. Ensure the directive appears near the top of every documentation page.

    Check your fix: curl -s https://documentation.ai/ | grep -n llms.txt finds the link near the top of the HTML.

  • llms.txt links work

    Not finished: robots.txt asked our scanner not to read some pages this check needed, and we follow it, so it is left out of the score. (All 15 same-origin sampled links resolve (101 total links) (1 external link also failed; may be bot-detection or rate-limiting))

  • llms.txt exists

    llms.txt found at 2 locations; using https://documentation.ai/llms.txt as canonical

  • llms.txt follows the standard structure

    llms.txt follows the proposed structure (H1, blockquote, heading-delimited link sections)

  • llms.txt fits in an agent's context

    llms.txt is 23,008 characters (under 50,000 threshold)

  • Markdown pages point agents to llms.txt

    llms.txt directive found in markdown of all 11 sampled pages, near the top of content; 4 had no markdown version

Markdown availability2 partly
  • Pages are available as Markdown

    11/14 sampled pages support .md URLs (79%); inconsistent support

    0 of 14 pages support .md URLs inconsistently. Ensure all documentation pages serve markdown when .md is appended to the URL.

    Check your fix: curl -sI https://documentation.ai/docs/ai/ai-documentation-agent.md returns 200 with a text/markdown or text/plain content type.

  • Server returns Markdown when asked

    Content negotiation partially supported: 11 correct type, 0 wrong type, 3 HTML only

    Your server returns markdown content for Accept: text/markdown requests but with an incorrect Content-Type header. Set the response Content-Type to text/markdown for proper agent handling.

    Check your fix: curl -sI -H "Accept: text/markdown" https://documentation.ai/ returns content-type: text/markdown.

Page size and truncation1 passed3 partly
  • Markdown pages fit in context

    2 of 11 pages between 50K–100K chars (max 59K)

    2 of 11 markdown pages are between 50K and 100K characters. These may be truncated on some agent platforms or routed through summarization. Consider splitting large pages.

  • HTML pages fit in context

    3 of 15 sampled pages convert to 50K–100K chars (max 1216K HTML → 64K markdown (89% boilerplate))

    3 of 15 pages convert to 50K-100K characters of markdown. Review pages for reducible boilerplate (navigation, serialized tabbed content). Consider providing markdown versions as a smaller alternative path for agents.

  • Content starts near the top

    3 of 15 sampled pages have content starting at 10–50% (worst 26%)

    3 of 15 pages have documentation content starting 10-50% into the converted output. Reduce navigation, breadcrumb, and sidebar markup that precedes the content area.

  • Content is in the HTML without JavaScript

    All 15 sampled pages contain server-rendered content

Content structure3 passed
  • Tabs don't bloat the page

    No tabbed content detected across 15 sampled pages

  • Headings inside tabs name their variant

    No tabbed content found; header quality check not applicable

  • Code blocks are well-formed

    All 74 code fences properly closed across 13 pages

URL stability2 passed
  • Missing pages return a real 404

    All 15 sampled pages return proper error codes for bad URLs

  • Redirects stay on the same host

    No redirects detected across 15 sampled pages

Content health2 passed1 partly
  • Markdown matches the HTML page

    4 of 11 pages have minor content differences between markdown and HTML

    4 pages have minor content differences between their markdown and HTML versions.

  • llms.txt covers the whole site

    llms.txt covers 95% of 202 sitemap doc pages; 4 llms.txt links not in sitemap (may indicate stale links or incomplete sitemap)

  • Cache headers allow timely updates

    All 17 endpoints have appropriate cache headers

Authentication and access1 passed
  • Gated docs offer another way in

    All docs pages are publicly accessible; no alternative access paths needed

  • Docs are readable without logging in

    All 15 sampled pages are publicly accessible

Crawler access1 passed1 failed
  • Sitemap lists the docs pages

    The sitemap at https://documentation.ai/sitemap.xml lists 85 of the 182 docs pages found through llms.txt and page links.

    Generate the sitemap from the same source as the docs, so every page is listed. Agents and crawlers use it to find pages that navigation does not link.

    Check your fix: curl -s https://documentation.ai/robots.txt | grep -i sitemap names a sitemap, and that sitemap lists the pages the report names as missing.

  • Crawlers and AI assistants may read the docs

    robots.txt lets Googlebot, Bingbot, OAI-SearchBot, PerplexityBot, Claude-SearchBot and Claude-User read the docs.

Freshness

Maintenance3 passed
  • Pages say when they were last changed

    13 of 14 sampled pages state when they were last changed.

  • Links and section anchors work

    All 38 links and 15 section anchors checked on the sampled pages work. 5 more could not be verified (timeouts or blocked requests) and are not counted.

  • Sitemap entries still exist

    All 10 sitemap entries sampled still exist.

Consistency with the API specNot applicable
  • Endpoints in the docs exist in the API spec

    No OpenAPI description was found, so the docs could not be compared with a spec.

CurrencyNot applicable
  • Deprecated operations are marked as such

    No OpenAPI description was found, so deprecation notices could not be compared with a spec.

Additional checks

Not part of the score: optional extras that help agents use your docs.

  • MCP server is discoverable

    An MCP server answers at https://mcp.documentation.ai/mcp; agents need to sign in to use it.

  • llms-full.txt is available

    No llms-full.txt found at https://documentation.ai/llms-full.txt.

    Publish /llms-full.txt with the full text of your docs in Markdown, so an agent can load everything in one request instead of crawling page by page.

    Check your fix: curl -sI https://documentation.ai/llms-full.txt returns 200.

  • Agent skills are published

    No agent skills index was found at /.well-known/agent-skills/index.json.

    Publish an Agent Skills index at /.well-known/agent-skills/index.json with a SKILL.md for your main tasks, so agents can load task instructions without reading every page.

About this scan

Scanned
Oct 21, 2026
Pages tested
15 of 271 found
Platform
Documentation.AI
Kind of site
Developer docs
AFDocs score, on its own
90 (A), 13 of 23 checks pass
  • Based on 15 sampled pages, chosen deterministically from the sitemap and llms.txt. Pages outside the sample were not read.
  • Pages were fetched without running JavaScript, the way most AI agents read the web.
  • robots.txt stopped the scanner from reading 4 URLs; checks that needed them are unverified.
  • Some checks could not be verified (a timeout, a blocked request or a scan limit); they are left out of the score rather than counted as failures.
  • Answerability, where an AI agent answers real questions written from these pages, runs in the open-source scanner with your own API key. This web score is made of Access and Freshness.

Methodology 2026-09.6 · AFDocs 0.20.0

Pages we sampled (15)
  • https://documentation.ai/
  • https://documentation.ai/blog/document360-vs-documentation-ai
  • https://documentation.ai/blog/mintlify-alternatives
  • https://documentation.ai/blog/rss.xml
  • https://documentation.ai/docs/ai/ai-documentation-agent
  • https://documentation.ai/docs/api-reference/get-analytics-feedback-comments
  • https://documentation.ai/docs/api-reference/get-pull-requests
  • https://documentation.ai/docs/changelog
  • https://documentation.ai/docs/components/paramfield
  • https://documentation.ai/docs/customize/access-control/oauth
  • https://documentation.ai/docs/customize/site-configuration
  • https://documentation.ai/docs/help/contact-us
  • https://documentation.ai/docs/integrations/pirsch
  • https://documentation.ai/docs/organize/views
  • https://documentation.ai/docs/write-and-publish/web-editor

Show your score

Add the badge to your docs or README. It updates each time the site is scanned.

Agent Readiness Score badge

Markdown

[![Agent Readiness Score: 90 (A)](https://documentation.ai/agent-score/badge/documentation-2.svg)](https://documentation.ai/agent-score/documentation-2)

HTML

<a href="https://documentation.ai/agent-score/documentation-2"><img src="https://documentation.ai/agent-score/badge/documentation-2.svg" alt="Agent Readiness Score: 90 (A)" height="20"></a>

Agent-ready docs by default

Documentation.AI sites ship with llms.txt, Markdown pages, a sitemap and an MCP server, and our agent keeps the content current.

Live in under 5 min · No credit card required