developer docs benchmark

developers.expanse.host benchmark.

Report for

developers.expanse.hostdevelopers.expanse.host

Agents should be able to find the right page, fetch the content, and follow the instructions without much extra guesswork. This developer docs benchmark shows where agents can use these docs cleanly and where the biggest points of friction still are.

Last checked: May 10, 2026Category: DocsAlot runsBenchmark type: developer docs benchmarkSource: DocsAlot run

Benchmark score

96Grade 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

Key takeaways

What stands out in this benchmark.

Start with what already works, then move to the fixes most likely to lift the score.

Working now

What already works.

LLMS TXT exists
Markdown parity exists
LLMS TXT is structured

Improve next

What to improve next.

Support Accept: text/markdown content negotiation

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 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://developers.expanse.host/llms.txt (2021 chars)

LLMS Full exists

Found llms-full.txt at https://developers.expanse.host/llms-full.txt (2239 chars)

Markdown parity exists

5/5 sampled pages have valid .md versions. Pages sourced from llms.txt. Checked: ✓ https://developers.expanse.host/index.html.md, ✓ https://developers.expanse.host/getting-started.md, ✓ https://developers.expanse.host/authentication.md, ✓ https://developers.expanse.host/pricing.md, ✓ https://developers.expanse.host/api-reference.md

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 3 H2 sections; ✓ Has list items with links

Links include descriptions

8/8 links have descriptions

Docs sections are structured

Found 3 recognized section types in H2 headings. Your sections: "guides", "api reference", "optional"

Optional sections are separated

Has an ## Optional section - AI tools can skip this content when context window is limited

Task readiness

4 passed1 failed

Can an agent follow the instructions without guessing?

This area is usable, but it still adds avoidable friction.

Product description is clear

Blockquote description has 38 words

Constraints are documented

Found constraint indicators: constraint, authentication, api key

Integrations are documented

Found integration references: integration, webhook

Error handling is documented

Found error/troubleshooting references: error, fix, issue

Examples are included

No code examples or example sections found

Access and recovery

4 passed1 failed

Can an agent complete the task without getting blocked?

This area is usable, but it still adds avoidable friction.

Markdown routes resolve

5/5 markdown pages return valid markdown content

Pages respond quickly

Average response time: 28ms across 7 requests

Content is readable without JS

Content is present in the initial HTML response (server-rendered)

Markdown negotiation works

None of the 3 tested pages return markdown via content negotiation (Accept: text/markdown). Checked: ✗ https://developers.expanse.host/index.html, ✗ https://developers.expanse.host/getting-started, ✗ https://developers.expanse.host/authentication

Markdown output stays clean

4/5 markdown pages have clean content without nav/footer cruft

Next steps