Agent readiness · Error monitoring
sentry.io
10 of 15 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with. 1 of them could not be measured from where we ask, and those are left out of the denominator rather than counted as failures.
A · Discovery
- PASSAnswers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
- PASSllms.txt publishedllms.txt present at https://sentry.io/llms.txt and https://docs.sentry.io/llms.txt, and the 12 links we sampled across the file all answer
- FAILDocs readable without JavaScriptOnly 1,863 characters render without JS, on https://docs.sentry.io/platforms/apple/data-management/ rather than on https://docs.sentry.io/
- PASSOn-demand agents not blockedNo on-demand agent is blocked
- N/APaths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
- PASSNo punishing crawl delayNo Crawl-delay applies to the agents we check
B · Agent entry
- PARTAgent entry pointOnly service descriptors: https://sentry.io/.well-known/mcp.json. No procedure written for a machine.
- PASSOAuth dynamic client registrationregistration_endpoint published, but none of the 2 advertised grants (authorization_code, refresh_token) finishes without a person at a browser
- PASSMCP surfaceLive MCP endpoint at https://mcp.sentry.dev/mcp, answered 401 with an auth challenge
C · Registration
- FAILNo CAPTCHA in the signup HTMLrecaptcha appears in the signup page's server HTML
- PASSSignup reachable without a browserForm renders in server HTML at https://sentry.io/signup/
D · Provisioning
- FAILProgrammatic key provisioningNone of the 7 provisioning phrases appears in the 6 documents we read
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://sentry.io/pricing/: "$0", "Free Developer Plan"
E · Integration
- PASSTyped SDK on the registry@sentry/browser@10.70.0 ships types
- UNMEASUREDMachine-readable API descriptionUnmeasurable: the site answers unknown markdown paths with text, so the markdown it served is not evidence of negotiation
Tell me when this changes
The failures here are the kind nobody notices. An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rescan weekly and write only when a verdict moves.
This page is the newest scan we hold for sentry.io and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.