Agent-Readiness Score
Are your docs ready for agents?
Paste a docs URL. We check llms.txt, markdown twins, citation density, nav completeness, robots hints, and MCP signals — then return a 0–100 score you can badge.
The Agent-Readiness Score answers whether coding agents can actually read a documentation site: markdown twins, llms.txt, navigation completeness, citation density, heading structure, robots hints, MCP, and Ask AI.
- users onboarded
- 640+
- doc modules generated
- 18k+
- files indexed
- 2.1M+
- avg to first docs
- ~2 min
What does Agent-Readiness Score check?
- llms.txt and markdown twins for every documentation page
- Navigation completeness: every page reachable from the docs nav
- Citation density: sections that name the files they describe
- Heading structure, robots allowances, MCP availability, and Ask AI access
How does Agent-Readiness Score work?
- 1.Enter the URL of a public documentation site.
- 2.ShipDocs inspects the served HTML, markdown twins, and machine-readable files.
- 3.You get a score out of 100 with per-check fixes and an embeddable badge.
What do you get from Agent-Readiness Score?
- • A 0-100 agent-readiness score with a letter grade
- • The exact checks failing and how to fix each one
- • An embeddable badge for your README
“Every AI tool invented APIs we don't have. ShipDocs cited src/routes/billing.ts on the first question. That alone paid for Advanced.”
Frequently asked questions
Why does agent readiness matter for SEO?
- AI assistants answer with what they can read. Sites that serve clean markdown, clear headings, and citations get quoted more often.
What is a markdown twin?
- A plain .md version of a documentation page at the same URL with a .md suffix, so an agent can read it without parsing HTML.
How does ShipDocs score?
- ShipDocs portals ship llms.txt, markdown twins, cited sections, and an MCP endpoint by default, which is why they score in the A range.
More free tools and examples
- Repo Wrapped — Shareable stats card for any public repo: languages, hotspots, doc coverage.
- Onboarding Time Estimator — How long a new engineer needs to ship their first change in your repo.
- Docs Gap Map — Which files and modules have no documentation at all.
- Dependency Time Bomb — Outdated, unmaintained and risky dependencies, ranked by upgrade pain.
- Dead Code Finder — Unused files, exports and dependencies that can safely be deleted.
- Production Readiness Audit — Tests, CI, error handling, secrets and deployment hygiene in one report.
- Architecture Diagram — A Mermaid diagram of modules and their real import relationships.
- Repo Complexity Score — Cyclomatic complexity, nesting depth and the files that slow teams down.
All free developer tools · Live examples of generated documentation · How ShipDocs works
By The ShipDocs team · Reviewed