---
title: "Docs Benchmark Report: developers.expanse.host"
description: "developers.expanse.host benchmark report with category scores and check-level detail."
canonical: "https://docsalot.dev/benchmarks/docs/developers-expanse-host"
human_url: "https://docsalot.dev/benchmarks/docs/developers-expanse-host"
markdown_url: "https://docsalot.dev/benchmarks/docs/developers-expanse-host.md"
index_url: "https://docsalot.dev/benchmarks/docs"
index_markdown_url: "https://docsalot.dev/benchmarks/docs.md"
updated: "2026-05-10"
---

[Back to docs benchmark index](https://docsalot.dev/benchmarks/docs.md)

# Docs Benchmark Report: developers.expanse.host

> Copy this markdown report into a developer ticket or coding agent prompt when you want concrete docs fixes tied to benchmark checks.

## Report Links

- Human report: https://docsalot.dev/benchmarks/docs/developers-expanse-host
- Markdown report: https://docsalot.dev/benchmarks/docs/developers-expanse-host.md
- Benchmark index: https://docsalot.dev/benchmarks/docs
- Benchmark index markdown: https://docsalot.dev/benchmarks/docs.md
- Public docs URL: https://developers.expanse.host/

## Score Summary

- Report for: developers.expanse.host
- Display URL: developers.expanse.host
- Report type: Public benchmark report
- Score: 96
- Grade: Excellent
- Summary: Agents should be able to find the right page, fetch the content, and follow the instructions without much extra guesswork.
- Checked at: May 10, 2026 at 2:29 AM UTC
- Category: DocsAlot runs
- Source: DocsAlot run
- Checks passed: 15/17
- Warnings: 0
- Failed checks: 2
- Skipped checks: 0

## What Already Works

- LLMS TXT exists
- Markdown parity exists
- LLMS TXT is structured

## What To Improve Next

- Support Accept: text/markdown content negotiation

## Full Score Breakdown

### Discovery and delivery - 100/100

- Question: Can an agent find the docs and fetch readable text?
- Category focus: Entry points, markdown access, and machine-readable delivery
- Category note: This area is already easy for agents to work through.
- Passed: 3
- Warnings: 0
- Failed: 0
- Skipped: 0

Checks:
- PASS - LLMS TXT exists: Found llms.txt at https://developers.expanse.host/llms.txt (2021 chars)
- PASS - LLMS Full exists: Found llms-full.txt at https://developers.expanse.host/llms-full.txt (2239 chars)
- PASS - 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 - 100/100

- Question: Can an agent understand how the page is organized?
- Category focus: Headings, navigation, and readable section hierarchy
- Category note: This area is already easy for agents to work through.
- Passed: 4
- Warnings: 0
- Failed: 0
- Skipped: 0

Checks:
- PASS - LLMS TXT is structured: ✓ Has H1 title; ✓ Has blockquote description; ✓ Has 3 H2 sections; ✓ Has list items with links
- PASS - Links include descriptions: 8/8 links have descriptions
- PASS - Docs sections are structured: Found 3 recognized section types in H2 headings. Your sections: "guides", "api reference", "optional"
- PASS - Optional sections are separated: Has an ## Optional section - AI tools can skip this content when context window is limited

### Task readiness - 88/100

- Question: Can an agent follow the instructions without guessing?
- Category focus: Examples, prerequisites, and action-ready instructions
- Category note: This area is usable, but it still adds avoidable friction.
- Passed: 4
- Warnings: 0
- Failed: 1
- Skipped: 0

Checks:
- PASS - Product description is clear: Blockquote description has 38 words
- PASS - Constraints are documented: Found constraint indicators: constraint, authentication, api key
- PASS - Integrations are documented: Found integration references: integration, webhook
- PASS - Error handling is documented: Found error/troubleshooting references: error, fix, issue
- FAIL - Examples are included: No code examples or example sections found

### Access and recovery - 80/100

- Question: Can an agent complete the task without getting blocked?
- Category focus: Public access, cleaner output, and fewer dead ends
- Category note: This area is usable, but it still adds avoidable friction.
- Passed: 4
- Warnings: 0
- Failed: 1
- Skipped: 0

Checks:
- PASS - Markdown routes resolve: 5/5 markdown pages return valid markdown content
- PASS - Pages respond quickly: Average response time: 28ms across 7 requests
- PASS - Content is readable without JS: Content is present in the initial HTML response (server-rendered)
- FAIL - 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
- PASS - Markdown output stays clean: 4/5 markdown pages have clean content without nav/footer cruft


## Suggested Handoff

Ask the developer or coding agent to work through the failed checks and next-step items first, then rerun the benchmark on https://developers.expanse.host/ to confirm the score moves in the right direction.