Stellar
Last scanned developers.stellar.org/docsDocusaurus15 pages tested
AI agents can find, read and use these docs well. Stellar scores 92 out of 100 (grade A), passing 20 of 26 checks. 6 still need work.
Developer docs
Kind of site
20/26
Checks passed
2
Partly passed
4
Failed
Access
Content discoverability4 passed1 failed2 partly
Markdown pages point agents to llms.txt
No llms.txt directive found in markdown of any of 15 sampled pages
No llms.txt directive was detected in the markdown of any tested page. Add a blockquote near the top of each markdown page (e.g., "> For the complete documentation index, see [llms.txt](/llms.txt)").
Check your fix: The Markdown version of https://developers.stellar.org/docs/build (its .md URL, or the page fetched with
Accept: text/markdown) has the llms.txt line in its first few lines.llms.txt follows the standard structure
llms.txt contains parseable links but doesn't fully follow the proposed structure: https://developers.stellar.org/llms.txt: No blockquote summary found
Your llms.txt contains parseable links but doesn't follow the standard structure. Add an H1 title as the first line and a blockquote summary (lines starting with >) to improve agent parsing.
Check your fix: llms.txt starts with a
# Title, then a> summaryline, then##sections of links.Pages point agents to llms.txt
llms.txt directive found in HTML of 15 of 15 sampled pages, but buried deep in the page (past 50%)
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://developers.stellar.org/docs/build | grep -n llms.txtfinds the link near the top of the HTML.llms.txt exists
llms.txt found at https://developers.stellar.org/llms.txt
llms.txt fits in an agent's context
llms.txt is 15,006 characters (under 50,000 threshold)
llms.txt links work
All 15 same-origin sampled links resolve (117 total links)
llms.txt links point to Markdown
15/15 same-origin sampled links point to markdown content (100%)
Markdown availability2 passed
Pages are available as Markdown
15/15 sampled pages support .md URLs (100%)
Server returns Markdown when asked
15/15 sampled pages support content negotiation (100%)
Page size and truncation3 passed1 failed
Content starts near the top
8 of 15 sampled pages have content starting past 50% (worst 78%)
8 of 15 pages have content starting past 50% of the converted output. Agents may never see the documentation content. 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
Markdown pages fit in context
All 15 pages under 50K chars (median 1K, max 10K)
HTML pages fit in context
All 15 sampled pages under 50K chars (median 57K HTML โ 13K markdown (76% boilerplate))
Content structure2 passed
Headings inside tabs name their variant
1 page(s) with tabs found, but no section headers inside tab panels to evaluate
Tabs don't bloat the page
1 tab group(s) across 1 of 15 sampled pages; all serialize under 50K chars
Code blocks are well-formed
All 8 code fences properly closed across 16 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 health1 passed2 failed
llms.txt covers the whole site
llms.txt covers 88/880 sitemap doc pages (10%); 792 missing
Your llms.txt covers 10% of your site's pages (below 80% threshold). 792 live pages are missing from the index. If unintentional, regenerate llms.txt from your sitemap or build pipeline. If intentional, lower the threshold or set it to 0 to make the check informational.
Markdown matches the HTML page
3 of 15 pages have substantive content differences between markdown and HTML (avg 19% missing)
3 pages have substantive content differences between markdown and HTML (avg 19% missing). If unintentional, agents are getting outdated content; regenerate markdown from source or fix the build pipeline.
Cache headers allow timely updates
All 16 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 access2 passed
Crawlers and AI assistants may read the docs
robots.txt lets Googlebot, Bingbot, OAI-SearchBot, PerplexityBot, Claude-SearchBot and Claude-User read the docs.
Sitemap lists the docs pages
The sitemap at https://developers.stellar.org/sitemap.xml lists 218 of the 218 docs pages found through llms.txt and page links.
Freshness
Maintenance3 passed
Pages say when they were last changed
15 of 15 sampled pages state when they were last changed.
Links and section anchors work
All 41 links and 15 section anchors checked on the sampled pages work. 1 more could not be verified (timeouts or blocked requests) and is 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
No MCP server was found for these docs.
Offer a read-only MCP server with a search tool over your docs, and link it from llms.txt, so agents in Cursor, Claude and ChatGPT can query your docs directly.
llms-full.txt is available
llms-full.txt found at https://developers.stellar.org/llms-full.txt (4,688,203 characters).
Agent skills are published
7 agent skills published at https://developers.stellar.org/.well-known/agent-skills/index.json.
About this scan
- Scanned
- Oct 21, 2026
- Pages tested
- 15 of 88 found
- Platform
- Docusaurus
- Kind of site
- Developer docs
- AFDocs score, on its own
- 90 (A), 15 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 2 URLs; checks that needed them are unverified.
- 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://developers.stellar.org/docs/build
- https://developers.stellar.org/docs/build/apps/guestbook/overview
- https://developers.stellar.org/docs/build/guides
- https://developers.stellar.org/docs/build/guides/conversions
- https://developers.stellar.org/docs/build/guides/storage
- https://developers.stellar.org/docs/build/smart-contracts/example-contracts
- https://developers.stellar.org/docs/data/analytics/hubble
- https://developers.stellar.org/docs/data/apis/rpc/providers
- https://developers.stellar.org/docs/learn/fundamentals/anchors
- https://developers.stellar.org/docs/learn/fundamentals/stellar-consensus-protocol
- https://developers.stellar.org/docs/learn/interactive
- https://developers.stellar.org/docs/platforms/stellar-disbursement-platform
- https://developers.stellar.org/docs/tokens/quickstart
- https://developers.stellar.org/docs/tools/developer-tools
- https://developers.stellar.org/docs/tools/ramps/moneygram
Show your score
Add the badge to your docs or README. It updates each time the site is scanned.
Markdown
[](https://documentation.ai/agent-score/stellar)HTML
<a href="https://documentation.ai/agent-score/stellar"><img src="https://documentation.ai/agent-score/badge/stellar.svg" alt="Agent Readiness Score: 92 (A)" height="20"></a>Agent-ready docs by default
Live in under 5 min ยท No credit card required