Static pre-check · Tue, 25 Aug 2026 01:10:14 GMT
AI agents can discover and access the site well, but encounter significant usability friction with incomplete content structure and limited machine-readable data.
Watch a real agent use your site →
A live Claude Code run against autumn.ai, streamed step by step.
Measure this with real agents →
An audit: measured success rates from repeated real agent runs, with confidence intervals and downloadable evidence.
2 API link(s), e.g. https://api.autumn.ai
https://www.autumn.ai
1 docs link(s), e.g. https://developer.mozilla.org
Shows the current scan score and grade for this domain, straight from the latest static pre-check.
[](https://www.vorza.dev/score/autumn.ai)<a href="https://www.vorza.dev/score/autumn.ai"><img src="https://www.vorza.dev/api/badge/autumn.ai" alt="agent readiness score" /></a>190 characters
'Autumn AI | AI People & Company Research' (40 chars)
og:title and og:description present
all 6 agent crawlers may fetch /
HTTP 200, 67 bytes
robots.txt has a Sitemap: line
16 URL(s) listed
registry lookup unavailable during this scan — excluded from the score rather than guessed
/llms-full.txt not served
Fix: Optional but cheap: publish /llms-full.txt with your docs inlined as one markdown file, so an agent can read everything in a single fetch.
Accept: text/markdown → text/html; charset=utf-8
Fix: Optional but increasingly expected: honour `Accept: text/markdown` by serving a markdown rendering of the page, so agents skip HTML parsing entirely.
ratio 0.0295 — 28139 readable chars in 952830 bytes of HTML
Fix: Most of what you serve is markup and inline script rather than content. Reduce inline payloads or server-render more text so the signal-to-noise ratio favours readers.
HTTP 200 for / (agent UA)
https://www.autumn.ai/
1 valid block(s)
HTTP 200, 3366 bytes
5 sampled link(s) all resolve
has headings and markdown links
both User-Agents got HTTP 200
28139 characters of text in the served HTML
0 redirect(s)
/docs not served (HTTP 404) — docs may live on another path or host
/agents.md not served (HTTP 404)
Fix: Publish /agents.md: what an agent may do here, which endpoints matter, auth requirements, and rate limits. It is the agent-facing counterpart to a README.
/docs → HTTP 404
Fix: Serve docs at the conventional /docs path, or redirect it to wherever they live. Agents try conventional paths first.
404 returns HTML, not a machine-readable body
Fix: Content-negotiate your errors: return a JSON body with a stable `code` (and a `next_action` where recovery exists) to clients that ask for JSON.
/openapi.json not served (HTTP 404)
Fix: If you have an HTTP API, publish its OpenAPI document at a predictable path (/openapi.json). It is the difference between an agent reading your contract and an agent guessing it. If you have no HTTP API, ignore this.
/.well-known/mcp.json not served (HTTP 404)
Fix: If you run an MCP server, advertise it at /.well-known/mcp.json so agents discover it without being told its URL.
/api → HTTP 404 (no API at the conventional root)
no MCP endpoint found to probe (none in the input URL and none advertised at /.well-known/mcp.json)
no listed MCP tools to inspect
no listed MCP tools to inspect
no MCP endpoint to probe
no parseable OpenAPI document
no parseable OpenAPI document
no parseable OpenAPI document
no parseable OpenAPI document
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.