Retrieved article excerpt
Open article · Retrieved 2026-10-10T08:24:28.579140+00:00
MENU ✕
Product
FEATURES
[AI-native platform Docs for humans and agents](https://www.veludocs.com/ai-native-documentation-platform/) [Agent V Answers with citations](https://www.veludocs.com/docs/ai/ask-ai) [Search Intent search across your docs](https://www.veludocs.com/docs/ai/search) [Components Prebuilt blocks for every page](https://www.veludocs.com/docs/components/overview) [Writing & editor Author pages in MDX or the browser](https://www.veludocs.com/docs/writing/pages)
AUTOMATION
[Self-updating docs Changes arrive as pull requests](https://www.veludocs.com/ai-native-documentation-platform/#docs-agent) [Writing with AI Use Claude Code, Codex or any AI tool](https://www.veludocs.com/docs/writing/writing-with-ai) [Publishing Push to main, Velu builds](https://www.veludocs.com/docs/deploy/publishing)
AGENT SURFACE
[llms.txt & markdown export Discovery, auto-maintained](https://www.veludocs.com/docs/ai/markdown-export) [skill.md Agents that can act on your docs](https://www.veludocs.com/docs/ai/skill-md) [MCP server Your docs as callable tools](https://www.veludocs.com/docs/ai/model-context-protocol) [Context menu One click into their AI tools](https://www.veludocs.com/docs/ai/contextual-menu) [Agent-friendly docs Score your docs against the spec](https://www.veludocs.com/agent-friendly-documentation/)
Solutions
USE CASES
[Developer documentation Docs that follow your code](https://www.veludocs.com/developer-documentation-software/) [Product documentation Docs level with every release](https://www.veludocs.com/product-documentation-software/) [Internal knowledge base Private docs for your team](https://www.veludocs.com/internal-knowledge-base-software/)
INDUSTRIES
[SaaS Docs that ship with every release](https://www.veludocs.com/solutions/documentation-for-saas/) [AI companies Docs humans and agents can read](https://www.veludocs.com/solutions/documentation-for-ai-companies/) [Developer tools Self-updating docs-as-code](https://www.veludocs.com/solutions/documentation-for-developer-tools/)
Resources
LEARN
[Documentation Guides, components, and setup](https://www.veludocs.com/docs/) [Blog Guides and comparisons](https://www.veludocs.com/blog/)
SEE VELU'S THEMES
[Vepa](https://vepa.veludocs.dev/) [Nila](https://nila.veludocs.dev/) [Thulir](https://thulir.veludocs.dev/) [Aalam](https://aalam.veludocs.dev/) [Kadhir](https://kadhir.veludocs.dev/)
[Pricing](https://www.veludocs.com/pricing/) [Log in](https://docs.getvelu.com/login)
AGENT-FRIENDLY DOCUMENTATION
# How agent-friendly is your documentation?
See your docs the way an agent does. 23 checks across 7 categories, scored against an open standard.
Open standard. No signup. Share your score with a link when you are done.
〉 WHAT GETS MEASURED
## Seven categories, twenty-three checks.
— / 100
SHARE YOUR SCORE
Post it to X, LinkedIn, or Reddit.
Copy link [Post on X](https://www.veludocs.com/agent-friendly-documentation/) [LinkedIn](https://www.veludocs.com/agent-friendly-documentation/) [Reddit](https://www.veludocs.com/agent-friendly-documentation/)
7 CHECKS
### Content Discoverability
llms.txt: whether it exists, is validly structured, stays under size, and whether your pages point to it.
View checks+
2 CHECKS
### Markdown Availability
Markdown at .md URLs, and a server that honours Accept: text/markdown.
View checks+
4 CHECKS
### Page Size and Truncation
Server-rendered content, 50K character budgets, and where your content starts.
View checks+
3 CHECKS
### Content Structure
Tabs that serialise, headers that stand alone, code fences that close.
View checks+
2 CHECKS
### URL Stability
Real 4xx codes instead of soft 404s, and same-host HTTP redirects.
View checks+
3 CHECKS
### Observability
Sitemap coverage, markdown that matches the HTML, and cache headers.
View checks+
2 CHECKS
### Authentication and Access
Pages that open without a login, or a documented alternative path.
View checks+
Scored against the [Agent-Friendly Documentation Spec ↗](https://agentdocsspec.com/spec/), an open community standard, using its MIT-licensed reference implementation.
〉 AGENT-READABLE BY DEFAULT
## Publish on Velu and the checks take care of themselves.
Everything measured above is part of what publishing does, not a project you schedule after the fact. Your pages go out human-readable and machine-readable at the same time, and they stay that way as you add to them.
01
### Auto llms.txt and llms-full.txt
Generated from your published docs and regenerated as pages are added, so agents always get a current index rather than one somebody remembered to update.
/llms.txt/llms-full.txt/page.md
02
### Markdown on every URL
Append .md to any page and get clean markdown back, without the navigation and layout markup an agent has to wade through.
03
### Server-rendered pages
Real content in the HTTP response. Nothing that needs JavaScript to appear, which is what most agents cannot execute.
04
### Managed hosting
Status codes, redirects, and cache headers handled by the platform, so URLs stay stable and updates get through.
05
### Public by default
Docs reachable without an interactive login, so an agent is not stopped at the door.
06
### MCP server and skill.md
One endpoint agents can search, read, and cite through, beyond what the spec asks for today.
agent → mcp.search() → your docs → cited answer
## The fine print, in plain English.
01 What is agent-friendly documentation? +
Agent-friendly documentation is documentation a model or agent can reliably find, fetch, parse, and act on. In practice that means pairing the human-readable pages with machine-readable artefacts: a discovery file like llms.txt, markdown versions of every page, server-rendered content that fits inside a context window, and stable URLs. Human readers can work around a gap by inferring or clicking around. Agents cannot, so they guess instead, and they do it confidently.
02 What is llms.txt? +
A plain-text index at the root of your docs that tells an agent what exists and where to read it. The convention is an H1 title, a blockquote summary, and headed sections of markdown links. It is the single highest-weighted item in the spec, because an agent that cannot discover your docs never reaches any of the other twenty-two checks.
03 How is the score calculated? +
By the Agent-Friendly Documentation Spec, an open community standard maintained at agentdocsspec.com. It defines 23 checks across 7 weighted categories. This page runs them with afdocs, the spec’s MIT-licensed reference implementation, against a sample of your pages, and reports exactly what it returns without adjustment.
04 Is this just SEO under a new name? +
No, and they can pull in opposite directions. SEO optimises how a page is ranked and presented to a human who will click, skim, and judge. This optimises whether a machine can retrieve the content at all, parse it without HTML noise, and fit it in a context window. A page can rank first on Google and still be unreadable to an agent, usually because it is client-rendered or buried under navigation markup.
05 What happens to the URL I enter? +
It is fetched, scored, and cached for fifteen minutes so repeat checks are fast. There is no signup and results are not published to a leaderboard. If you share your score, the link carries a signed summary of the result so others can open the same scorecard.
06 Can I share my score? +
Yes. After a run, copy the short link or share it to X, LinkedIn, or Reddit. Anyone with the link sees the same score, and the preview image shows the grade and overall score.
## Keep your docs agent-ready.
Publish a page and the machine-readable half comes with it, on every release.
[Get started for free →](https://docs.getvelu.com/signup) [Talk to founder](https://www.veludocs.com/contact/)
MADE FOR HUMANS & AGENTS · AI-NATIVE FROM DAY ONE