Static pre-check · Fri, 07 Aug 2026 06:50:24 GMT
sentry.io
AI agents lack machine-readable APIs and structured data, forcing them to parse HTML directly instead of using standard integration protocols.
Watch a real agent use your site →
A live Claude Code run against sentry.io, streamed step by step.
Test this with real agents →
An audit: measured success rates from repeated real agent runs, with confidence intervals and downloadable evidence.
Discovery 16.9/22.2
sitemap.xml exists and parsesdetailsFAIL
sitemap.xml not served (timeout after 8s)
Fix: Publish /sitemap.xml listing your public pages, and reference it from robots.txt with a `Sitemap:` line.
API reference linked from the homepagedetailsWARN
no link to an API reference in the homepage HTML
Fix: If you have an API, link its reference from the homepage. If you don't, this check is safe to ignore.
Homepage has a descriptive titledetailsWARN
title is 107 characters (truncated in most surfaces)
Fix: Trim the <title> to 70 characters or fewer so it is not cut off.
Canonical URL declareddetailsPASS
https://sentry.io/welcome/
Documentation linked from the homepagedetailsPASS
3 docs link(s), e.g. https://docs.sentry.io/
Homepage has a meta descriptiondetailsPASS
169 characters
Open Graph tags presentdetailsPASS
og:title and og:description present
robots.txt allows agent crawlersdetailsPASS
all 6 agent crawlers may fetch /
robots.txt existsdetailsPASS
HTTP 200, 140 bytes
robots.txt points at the sitemapdetailsPASS
robots.txt has a Sitemap: line
Brand findable in agent searchdetailsN/A
search-based checks are deferred — excluded from the score
Listed in an MCP registrydetailsN/A
registry lookup not implemented in v1 — excluded from the score rather than guessed
Accessibility 31.2/33.3
Serves markdown when asked for itdetailsWARN
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.
Content-to-markup ratio is reasonabledetailsWARN
ratio 0.0301 — 18884 readable chars in 627233 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.
Docs are readable without JavaScriptdetailsPASS
1114 characters of text at /docs
Homepage responds to an agent requestdetailsPASS
HTTP 200 for / (agent UA)
Served over HTTPSdetailsPASS
https://sentry.io/welcome/
Structured data (JSON-LD) on the homepagedetailsPASS
2 valid block(s) (WebPage, Organization)
llms-full.txt is publisheddetailsPASS
HTTP 200, 20402 bytes
llms.txt is publisheddetailsPASS
HTTP 200, 2112 bytes
Links in llms.txt resolvedetailsPASS
5 sampled link(s) all resolve
llms.txt is structured markdowndetailsPASS
has headings and markdown links
Same response for agents and browsersdetailsPASS
both User-Agents got HTTP 200
Homepage has readable text without JavaScriptdetailsPASS
18884 characters of text in the served HTML
No long redirect chain on the homepagedetailsPASS
1 redirect(s)
Usability 19.4/44.4
MCP server completes the initialize handshakedetailsFAIL
HTTP 401 — the endpoint requires credentials to initialize
Fix: Let unauthenticated clients complete `initialize` and `tools/list`, and require auth only on `tools/call`. An agent that cannot see your tools cannot decide to use them.
OpenAPI document publisheddetailsFAIL
/openapi.json is served but is not valid JSON
Fix: Serve a parseable OpenAPI document at /openapi.json. What is there now cannot be read by any tooling.
agents.md is publisheddetailsWARN
/agents.md returns HTML
Fix: Serve /agents.md as markdown (text/markdown or text/plain). An HTML page here is probably your SPA catch-all route.
Errors are machine-readabledetailsWARN
a nonexistent path returned HTTP 200, not 404
Fix: Return 404 for paths that do not exist. A 200 on a missing page makes an agent believe it found something.
A documentation endpoint respondsdetailsPASS
/docs → HTTP 200
.well-known/mcp.json advertises an MCP serverdetailsPASS
HTTP 200, valid JSON
The /api root behaves predictablydetailsN/A
/api did not respond (timeout after 8s)
MCP tool parameters are typed and describeddetailsN/A
no listed MCP tools to inspect
Every MCP tool has a descriptiondetailsN/A
no listed MCP tools to inspect
MCP server lists toolsdetailsN/A
handshake did not complete, so tools/list was not reached
OpenAPI declares its auth schemedetailsN/A
no parseable OpenAPI document
OpenAPI operations are describeddetailsN/A
no parseable OpenAPI document
OpenAPI documents error responsesdetailsN/A
no parseable OpenAPI document
OpenAPI document is structurally validdetailsN/A
no parseable OpenAPI document
Payments not applicable — excluded from the score
Serves a 402 payment challengedetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Declares AP2 / ACP supportdetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Publishes x402 payment metadatadetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Badge
Shows the current scan score and grade for this domain, straight from the latest static pre-check.
[](/score/sentry.io)<a href="/score/sentry.io"><img src="/api/badge/sentry.io" alt="agent readiness score" /></a>