sentry.io agentic web readiness

B Score 39 (coverage 30 + breadth 9 + conformance 0). 5 standards observed across 3 of 9 steps; 6 manifests present, 5 errors, 9 warnings. Checked 2026-10-19 23:59:54 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	not fetched: subrequest-limit
AI Catalog well-known file `/.well-known/ai-catalog.json`	absent	not fetched: subrequest-limit
MCP Server Cards (SEP-2127) `/.well-known/mcp.json`	errors HTTP 200	$schema missing (required: https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json) name must be reverse-DNS with exactly one slash, e.g. com.example/weather version missing Content-Type is application/json; SEP-2127 says serve application/mcp-server-card+json remotes missing: a card with no remotes gives clients nothing to connect to no Access-Control-Allow-Origin: * (required for browser clients) no ETag
Agent2Agent Protocol `/.well-known/agent-card.json`	absent	not fetched: timeout
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`	absent	not fetched: subrequest-limit
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
security.txt (RFC 9116): RFC 9116 contact and expiry, read by agents and people

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