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

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

# Docs Benchmark Report: docs.eco.com

> 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/docs-eco-com
- Markdown report: https://docsalot.dev/benchmarks/docs/docs-eco-com.md
- Benchmark index: https://docsalot.dev/benchmarks/docs
- Benchmark index markdown: https://docsalot.dev/benchmarks/docs.md
- Public docs URL: https://docs.eco.com/

## Score Summary

- Report for: docs.eco.com
- Display URL: docs.eco.com
- Report type: Public benchmark report
- Score: 102
- 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 19, 2026 at 5:20 PM UTC
- Category: DocsAlot runs
- Source: DocsAlot run
- Checks passed: 16/17
- Warnings: 0
- Failed checks: 1
- Skipped checks: 0

## What Already Works

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

## What To Improve Next

- Examples are included

## 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://docs.eco.com/llms.txt (11890 chars)
- PASS - LLMS Full exists: Found llms-full.txt at https://docs.eco.com/llms-full.txt (275408 chars)
- PASS - Markdown parity exists: 5/5 sampled pages have valid .md versions. Pages sourced from llms.txt. Checked: ✓ https://docs.eco.com/get-started/what-is-eco.md, ✓ https://docs.eco.com/get-started/choose-your-product.md, ✓ https://docs.eco.com/get-started/quickstart.md, ✓ https://docs.eco.com/solutions/wallets.md, ✓ https://docs.eco.com/solutions/protocols.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 12 H2 sections; ✓ Has list items with links
- PASS - Links include descriptions: 77/77 links have descriptions
- PASS - Docs sections are structured: Found 4 recognized section types in H2 headings. Your sections: "get started", "solutions for [persona]", "concepts", "routes", "routes architecture", "primitives", "programmable addresses", "programmable transactions", "recipes", "api reference", "resources", "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 80 words
- PASS - Constraints are documented: Found constraint indicators: require, constraint, authentication
- PASS - Integrations are documented: Found integration references: integration, sdk
- PASS - Error handling is documented: Found error/troubleshooting references: issue
- FAIL - Examples are included: No code examples or example sections found

### Access and recovery - 100/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 already easy for agents to work through.
- Passed: 5
- Warnings: 0
- Failed: 0
- Skipped: 0

Checks:
- PASS - Markdown routes resolve: 5/5 markdown pages return valid markdown content
- PASS - Pages respond quickly: Average response time: 733ms across 7 requests
- PASS - Content is readable without JS: Content is present in the initial HTML response (server-rendered)
- PASS - Markdown negotiation works: 3/3 pages return markdown when requested with Accept: text/markdown. Checked: ✓ https://docs.eco.com/get-started/what-is-eco, ✓ https://docs.eco.com/get-started/choose-your-product, ✓ https://docs.eco.com/get-started/quickstart
- PASS - Markdown output stays clean: Markdown content is clean (no navigation, footer, or cookie elements)


## 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://docs.eco.com/ to confirm the score moves in the right direction.