Prove

# Agent Score Fix Report — Prove
URL: https://developer.prove.com
Score: 59/100 (Grade F)

I need help improving the AI-readiness of the documentation at https://developer.prove.com.
Agent Score found 7 failing checks and 0 warnings.

## Failing Checks (7)
- [content-discoverability] Llms Txt Valid: llms.txt exists but contains no parseable links
- [content-discoverability] Llms Txt Directive Html: No llms.txt directive found in HTML of any of 1 pages
- [content-discoverability] Llms Txt Directive Md: Could not fetch markdown for any of 1 pages; 1 had no markdown version
- [markdown-availability] Markdown Url Support: No pages support .md URLs (0/1 tested)
- [markdown-availability] Content Negotiation: Server ignores Accept: text/markdown header (0/1 pages return markdown)
- [page-size] Content Start Position: 1 of 1 pages have content starting past 50% (worst 68%)
- [url-stability] Http Status Codes: 1 of 1 pages return 200 for non-existent URLs (soft 404)



## Fix Instructions

For each issue above, please:
1. Analyze the documentation site at https://developer.prove.com
2. Implement the specific fix
3. Verify the fix would cause the check to pass

### Common fixes:
- **No llms.txt**: Create /llms.txt following https://llmstxt.org — list all doc pages in markdown format
- **No .md URL support**: Configure your docs platform to serve pages at equivalent .md URLs (e.g. /docs/quickstart.md)
- **No content negotiation**: Return markdown when request includes Accept: text/markdown header
- **Large page size**: Reduce nav boilerplate, inline scripts, and repetitive markup
- **No sitemap**: Generate /sitemap.xml listing all documentation URLs
- **Auth walls**: Ensure docs pages return 200 without requiring login cookies or tokens
- **No Last-Modified header**: Configure your server/CDN to include Last-Modified response headers
- **Tab content hidden**: Ensure tabbed content is rendered in the HTML (not JS-only) so agents can read all variants

## Run afdocs Locally for More Detail

To get deeper visibility into what's failing, run afdocs against your docs:

  npx afdocs check https://developer.prove.com --fixes --verbose

- **--fixes**: Adds "Fix:" lines to the output for each warn/fail check with actionable remediation steps
- **-v, --verbose**: Shows per-page details (specific URLs, character counts, error codes) for checks with issues — useful for per-URL visibility into what's failing