sentry.io agentic web readiness

B Score 44 (coverage 30 + breadth 9 + conformance 5). 5 standards observed across 3 of 9 steps; 6 manifests present, 4 errors, 6 warnings. Checked 2026-10-20 05:32:07 UTC. This grades the agent-facing files published at sentry.io, not the organisation's products.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/sentry.io.svg) · JSON · Markdown · Re-check now

Coverage by step

01 DiscoverRFC 9727, agents.txt 02 Identifynothing observed 03 PermitOAuth Protected Resource and Authorization Server Metadata (as used for agent authorization)04 Readllms.txt, AGENTS.md 05 Actnothing observed 06 Coordinatenothing observed 07 Paynothing observed 08 Presentnothing observed 09 Accountnothing observed

Manifests

Manifest	Result	Findings
Agentic Resource Discovery `/.well-known/ard.json`	absent HTTP 200	answered with an HTML page (catch-all or soft 404), counted as absent
AI Catalog well-known file `/.well-known/ai-catalog.json`	absent HTTP 200	answered with an HTML page (catch-all or soft 404), counted as absent
MCP Server Cards (SEP-2127) `/mcp/server-card`	absent HTTP 200	answered with an HTML page (catch-all or soft 404), counted as absent
Agent2Agent Protocol `/.well-known/agent.json`	absent HTTP 200	answered with an HTML page (catch-all or soft 404), counted as absent
llms.txt `/llms.txt`	valid HTTP 200	file is large; keep llms.txt an index and put the full text in llms-full.txt
AGENTS.md `/AGENTS.md`	valid HTTP 200
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs `/.well-known/api-catalog`	valid HTTP 200
AI Crawler User-Agent Tokens in robots.txt `/robots.txt`	errors HTTP 200	no User-agent group at all no AI crawler token named (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, ...); the policy for them is whatever User-agent: * says (unspecified) no Sitemap: line no Agentmap: line (optional convention pointing agents at /.well-known/ard.json) no Content-Signal: line (optional; states ai-train / search / ai-input preferences)
security.txt (RFC 9116) `/.well-known/security.txt`	errors HTTP 200	Contact: security@sentry.io is not a mailto:, https: or tel: URI Expires: missing (RFC 9116 requires it) Canonical: missing
auth.md `/auth.md`	errors HTTP 200	none of the auth.md mechanism names found (identity_assertion, service_auth, anonymous)

What an agent can call

llms.txt: Sentry, 337 links
robots.txt AI policy: unlisted crawlers unspecified
OAuth protected resource https://sentry.io, authorization servers: https://sentry.io

Standards observed

llms.txt https://sentry.io/llms.txt
AGENTS.md https://sentry.io/AGENTS.md
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://sentry.io/.well-known/api-catalog
agents.txt https://sentry.io/agents.txt
OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization) https://sentry.io/.well-known/oauth-protected-resource

Cheapest next steps

Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch
MCP Server Cards (SEP-2127): if you run an MCP server, a SEP-2127 card at <mcp-url>/server-card lets clients configure themselves

How the grade is made

+10 per lifecycle step with a standard observed, counting manifests that validate or that the probe rule for the standard recognises (a valid MCP server card counts for MCP; max 90); +3 per observed standard beyond the first two (max 15); conformance +15 (+10 with one manifest) minus 5 per agent-facing manifest with errors, never below 0 (security.txt is reported, not scored). A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Errors are specification violations; warnings are best-practice gaps. Only public paths are fetched, without credentials, so standards that need a login (skipped in the probe) are not counted either way. The same report is the validate_manifest tool on the MCP server.

JSON · Markdown · probe rules