mercury.com

no link to documentation found in the homepage HTML

Fix: Link your docs from the homepage with visible anchor text ("Docs", "Documentation", "Developers"). An agent that cannot find your docs from your homepage will guess your API.

robots.txt not served (HTTP 429)

Fix: Serve a /robots.txt. Without it, agent crawlers have to guess what they may fetch.

sitemap.xml not served (HTTP 429)

Fix: Publish /sitemap.xml listing your public pages, and reference it from robots.txt with a `Sitemap:` line.

title is 98 characters (truncated in most surfaces)

Fix: Trim the <title> to 70 characters or fewer so it is not cut off.

2 API link(s), e.g. /api

https://mercury.com

121 characters

og:title and og:description present

search-based checks are deferred — excluded from the score

registry lookup not implemented in v1 — excluded from the score rather than guessed

no robots.txt to evaluate — nothing is blocked by rules that don't exist

no robots.txt

HTTP 429 for an agent User-Agent

Fix: Return 200 for agent requests to the homepage. A non-2xx here means nothing downstream can be evaluated.

/llms.txt not served (HTTP 429)

Fix: Publish /llms.txt: a plain-markdown index that tells an agent what this product is and where the authoritative docs live. It is the cheapest high-leverage file you can add.

browser got HTTP 200, agent User-Agent got HTTP 429

Fix: Your CDN or WAF is blocking non-browser clients. Allow well-identified bots, or at least return a 200 with readable content instead of a challenge page.

/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.0097 — 8223 readable chars in 846834 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.

https://mercury.com/

1 valid block(s)

8223 characters of text in the served HTML

0 redirect(s)

/docs not served (HTTP 429) — docs may live on another path or host

no llms.txt

no llms.txt to parse

/agents.md not served (HTTP 429)

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 429

Fix: Serve docs at the conventional /docs path, or redirect it to wherever they live. Agents try conventional paths first.

a nonexistent path returned HTTP 429, not 404

Fix: Return 404 for paths that do not exist. A 200 on a missing page makes an agent believe it found something.

/openapi.json not served (HTTP 429)

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 429)

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 429 (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.