Working well
Where the docs already help.
- LLMS TXT exists.
- Markdown parity exists.
- LLMS TXT is structured.
For the broader pattern behind these wins, review AI-readable documentation and compare this page with the full docs benchmark leaderboard.
Documentation benchmark
kitaru-site-preview-303.zenml-migration.workers.dev/docs benchmark
Report for
kitaru-site-preview-303.zenml-migration.workers.dev/docskitaru-site-preview-303.zenml-migration.workers.dev/docs
Agents should be able to find the right page, fetch the content, and follow the instructions without much extra guesswork. This Documentation benchmark shows where agents can use these docs cleanly and where the biggest points of friction still are.
Benchmark score
97Grade Excellent
This report passes 15 of 17 checks, with 0 warnings, 2 failed checks, and 0 skipped checks still shaping the next score lift.
- Checks passed
- 15/17
- Warnings
- 0
- Failed checks
- 2
Search page context
Why kitaru-site-preview-303.zenml-migration.workers.dev/docs matters as a documentation surface
Documentation quality now affects implementation speed, support load, and whether an agent or buyer can stay self-serve. This benchmark shows where the docs already work well and where they still introduce friction.
Good documentation is discoverable, readable in plain text, clear about structure and instructions, and specific enough in examples and next steps that real workflows can keep moving.
What this report means
What this documentation benchmark says about kitaru-site-preview-303.zenml-migration.workers.dev/docs.
These are the clearest signals behind the current score. Start with the strengths that already support discovery and implementation, then use the gaps below to prioritize the fixes most likely to improve AI readability and self-serve onboarding.
Improve next
What to fix for better self-serve.
- List key constraints and requirements.
If you want to improve the system behind these gaps, start with API docs automation, the OpenAPI to CLI generator, and this guide to making docs AI-readable.
Check results
Full score breakdown
Open each category to review the checks behind the score and see exactly where agents still hit friction.
Discovery and delivery3 passedCan an agent find the docs and fetch readable text?
Discovery and delivery
3 passed
Can an agent find the docs and fetch readable text?
This area is already easy for agents to work through.
LLMS TXT exists
Found llms.txt at https://kitaru-site-preview-303.zenml-migration.workers.dev/docs/llms.txt (19000 chars)
LLMS Full exists
Found llms-full.txt at https://kitaru-site-preview-303.zenml-migration.workers.dev/docs/llms-full.txt (618695 chars)
Markdown parity exists
5/5 sampled pages have valid .md versions. No llms.txt links found - checked common paths. Checked: ✓ https://kitaru-site-preview-303.zenml-migration.workers.dev/docs/quickstart.md, ✓ https://kitaru-site-preview-303.zenml-migration.workers.dev/docs/getting-started.md, ✓ https://kitaru-site-preview-303.zenml-migration.workers.dev/docs/guide.md, ✓ https://kitaru-site-preview-303.zenml-migration.workers.dev/docs/api.md, ✓ https://kitaru-site-preview-303.zenml-migration.workers.dev/docs/reference.md
Content structure4 passedCan an agent understand how the page is organized?
Content structure
4 passed
Can an agent understand how the page is organized?
This area is already easy for agents to work through.
LLMS TXT is structured
✓ Has H1 title; ✓ Has blockquote description; ✓ Has 4 H2 sections; ✓ Has list items with links
Links include descriptions
173/173 links have descriptions
Docs sections are structured
Found 5 recognized section types in H2 headings. Your sections: "getting started", "guides", "api reference", "optional"
Optional sections are separated
Has an ## Optional section - AI tools can skip this content when context window is limited
Task readiness3 passed2 failedCan an agent follow the instructions without guessing?
Task readiness
3 passed2 failed
Can an agent follow the instructions without guessing?
This area is still slowing agents down and needs attention.
Product description is clear
Blockquote description has 24 words
Constraints are documented
No constraints, requirements, or important notes found in opening
Integrations are documented
Found integration references: integration, connect, sdk
Error handling is documented
Found error/troubleshooting references: error, troubleshoot, problem
Examples are included
No code examples or example sections found
Access and recovery5 passedCan an agent complete the task without getting blocked?
Access and recovery
5 passed
Can an agent complete the task without getting blocked?
This area is already easy for agents to work through.
Markdown routes resolve
5/5 markdown pages return valid markdown content
Pages respond quickly
Average response time: 112ms across 7 requests
Content is readable without JS
Content is present in the initial HTML response (server-rendered)
Markdown negotiation works
3/3 pages return markdown when requested with Accept: text/markdown. Checked: ✓ https://kitaru-site-preview-303.zenml-migration.workers.dev/docs/quickstart, ✓ https://kitaru-site-preview-303.zenml-migration.workers.dev/docs/getting-started, ✓ https://kitaru-site-preview-303.zenml-migration.workers.dev/docs/guide
Markdown output stays clean
Markdown content is clean (no navigation, footer, or cookie elements)
Next steps
Get this report in your inbox or track the score over time.
Save the report to a work email now, or tell us what kind of ongoing monitoring would be useful for this docs site.
Keep exploring
Use this report as a real search entry point.
Compare related benchmark reports, then move into the guides and tools that improve documentation benchmark scores.
Related report
docs.eco.com
Related report102/100 score in DocsAlot runs. Open the full documentation benchmark report.
docs.cdp.coinbase.com
Related report100/100 score in DocsAlot runs. Open the full documentation benchmark report.
developers.expanse.host
96/100 score in DocsAlot runs. Open the full documentation benchmark report.
Leaderboard
Browse the full docs benchmark leaderboard
Free toolCompare this documentation benchmark report with other public docs benchmark results.
Run the docs benchmark on your site
WorkflowScore your own API docs or developer docs and open the full public report.
Review the API docs automation workflow
WorkflowSee how docs, SDKs, CLIs, and agent-facing outputs can ship from one OpenAPI-driven system.
See the OpenAPI to CLI generator page
GuideUse the CLI page when the benchmark gaps are really onboarding and implementation gaps.
How to make your docs AI-readable
Use this guide when you want to improve the same categories this benchmark scores.
Built by DocsAlot
Need help improving the score?
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.