Sentry: the 360 agent-readiness check
Sentry scores 80 of 100 on Ora's agent-readiness scan, a B, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 3: a public API, OAuth, a command line. WebMCP registered and two agent files that do not validate.
On 9 November 2026 the public site at sentry.io scored 80 of 100 on Ora's agent-readiness scan, a B, in Ora's Infrastructure category. Ora probes a site the way an agent would: it requests pages with the agents' own user agents, reads robots.txt, looks for the files agents read, and tries the API, MCP and payment surfaces. This check reads the act layer first, because that is what the directory records, then the door, what an agent can read, and whether the company is found and recommended. Ora's one-line summary: Sentry offers strong discovery and developer SDK coverage, but lacks a published OpenAPI specification for agents to integrate against.
The score
| Layer | Asks | Points | Share |
|---|---|---|---|
| Usability | Can agents use it | 59.5 of 78 | 76% |
| Access | Can agents read it | 48 of 62 | 77% |
| Discovery | Can agents find and recommend it | 13 of 14 | 93% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade B | 80 of 100 | 80% |
What an agent can do
The surfaces an agent acts on: an API it can find and call, an MCP server, an agent card, OAuth metadata, a command line. This is the layer the directory records, so it comes first.
In the directory, Sentry sign-in required, tools not seen, not counted; the connector run of 4 November 2026 is on the entry page. Ora's MCP server check for the same domain reads partial; the two look for different things, the directory for a server that answers a handshake and lists tools, Ora for a server it can find from the site.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| MCP server / manifest mcp-server | Partial | 5 of 6 | MCP server detected at https://mcp.sentry.dev/mcp; it requires authentication. Presence is verified (5/6), but Ora could not inspect its tools or verify access scopes without credentials. |
| MCP well-known discovery mcp-well-known-discovery | Pass | 2 of 2 | MCP server discoverable at standard path https://sentry.io/.well-known/mcp.json |
| Public API with reachable endpoints public-api | Pass | 7 of 7 | REST API documentation found at https://docs.sentry.io/organization/data-storage-location.md. GraphQL endpoint at https://graphql.sentry.io/ is reachable; introspection requires authentication (API key / OAuth), |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | Documentation site found at https://docs.sentry.io |
| Developer portal developer-portal | Pass | 6 of 6 | Developer portal found at https://docs.sentry.io |
| OpenAPI spec published openapi-spec | Fail | 0 of 7 | No OpenAPI/Swagger specification found |
| API catalog (RFC 9727) api-catalog-rfc9727 | Pass | 2 of 2 | no detail published |
| A2A / agent-card a2a-agent-card | Fail | 0 of 2 | No A2A agent card found at /.well-known/agent-card.json |
| Agent discovery file agent-discovery-file | Partial | 1 of 2 | Found legacy /.well-known/agent-skills; /.well-known/agent-skills/index.json has an empty 'skills' array - add at least one skill entry |
| OAuth 2.0 support oauth-support | Pass | 5 of 5 | OAuth authorization server metadata at https://sentry.io (issuer=https://sentry.io) |
| OAuth Protected Resource metadata (RFC 9728) oauth-protected-resource | Pass | 2 of 2 | no detail published |
| auth.md exists auth-md-exists | Fail | 0 of 2 | No /auth.md found at site root |
| WebMCP support webmcp | Pass | 5 of 5 | Imperative WebMCP API detected (document.modelContext.registerTool in script bundle /_astro/webmcp.m80_-iWU.js). |
| NLWeb /ask endpoint nlweb-ask | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST |
| CLI tool available cli-tool | Pass | 3 of 3 | CLI package found on npm: @sentry/cli |
| Multi-language SDK packages rest-sdk-packages | Pass | 3 of 3 | SDK packages found across 4 ecosystems: npm, pypi, go, rubygems |
| Rate limit response headers rate-limit-headers | Fail | 0 of 2 | GraphQL introspection auth-gated and no header convention documented on GraphQL-tagged pages |
| Idempotency-Key support idempotency-key-support | Partial | 1 of 3 | GraphQL idempotency described in documentation at https://docs.sentry.io/api.md; not confirmed in the schema |
| JSON error responses json-error-responses | Fail | 0 of 4 | API does not return JSON error responses (or no API detected) |
At the door
What the site answers when a request arrives with an agent's user agent, and what robots.txt says to agents.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Not blocked by bot detection bot-detection | Pass | 2 of 2 | Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). |
| Agent crawler reachability agent-crawler-reachability | Pass | 2 of 2 | Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable |
| robots.txt AI crawler policy robots-ai-policy-quality | Pass | 2 of 2 | AI search crawlers: allowed in 18 of 18 checks (3 crawlers on 6 pages). AI training crawlers: allowed in 12 of 12 checks (2 crawlers on 6 pages), not scored. |
| robots.txt agent-user policy robots-agent-user-policy | Pass | 2 of 2 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://sentry.io/. Declared policy only; |
| Content behind auth docs-auth-gate | Pass | 2 of 2 | All 5 sampled pages are publicly readable (5 with substantive content) |
| Homepage not hidden from search noindex-directives | Pass | 1 of 1 | No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search. |
| Redirect hygiene redirect-hygiene | Pass | 1 of 1 | no detail published |
| Web Bot Auth directory web-bot-auth-directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found |
What an agent can read
Whether the text is in the first response, what the site publishes for agents, and how it describes itself to them.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Content without JavaScript content-no-js | Partial | 2 of 3 | Homepage: 15918 chars with H1, but 4.0% content ratio is below the 5% target. 5 of 5 sampled inner pages have text without JavaScript. |
| Page token budget page-token-budget | Pass | 1 of 1 | All 6 measured pages fit an agent context budget (largest ~4K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at https://sentry.io/sitemap-index.xml with multiple sitemaps entries |
| Sitemap freshness (lastmod) sitemap-lastmod | Fail | 0 of 1 | None of the 500 sampled sitemap entries carries a lastmod date. Add <lastmod> (W3C datetime) so agents can prioritize fresh content. |
| llms.txt exists llms-txt-exists | Pass | 1 of 1 | Found the llms.txt at https://sentry.io/llms.txt. |
| llms.txt formatting llms-txt-formatting | Partial | 1 of 2 | The llms.txt at https://sentry.io/llms.txt is well-formatted with markdown links, but at 93,154 characters it exceeds the 30,000-character recommendation for a navigation index. |
| llms.txt links resolve llms-txt-links-resolve | Pass | 2 of 2 | no detail published |
| Markdown agent docs markdown-negotiation | Pass | 1 of 1 | Returns markdown when requested via Accept header |
| Markdown URL fallback markdown-url-fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://sentry.io/index.md and it did not return markdown (expected text/markdown content-type or a heading-led non-HTML body). |
| Bot-UA markdown serving agent-ua-markdown | Pass | 1 of 1 | https://sentry.io serves markdown to the ChatGPT-User User-Agent even with Accept: text/html - UA-sniffed agent responses in place |
| Agent mode view agent-mode-view | Fail | 0 of 2 | ?mode=agent returns same content as homepage (no dedicated agent view) |
| JSON-LD structured data json-ld | Pass | 4 of 4 | Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (2 block(s)) |
| Organization schema completeness org-schema-completeness | Partial | 1 of 2 | Organization schema found but missing: contactPoint |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Pass | 2 of 2 | no detail published |
| Schema type breadth schema-type-breadth | Fail | 0 of 2 | No extended schema types found - AI can only answer basic questions about this entity |
| Metadata completeness metadata-completeness | Pass | 2 of 2 | All metadata signals present: canonical URL, lang="en", og:image, og:type |
| Agent instruction / when-to-use agent-instruction | Partial | 2 of 3 | Agent instruction file at /agent.txt but no explicit when-to-use guidance |
Found and recommended
Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Brand name discoverability brand-search-accuracy | Pass | 3 of 3 | sentry.io ranks #5 for "Sentry" (searched your brand name alone: no main product term from your homepage qualified) |
| Wikipedia / Wikidata entity presence wikipedia-presence | Partial | 2 of 4 | Wikidata Q140835305 (Q140835305) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage |
| Developer resource discoverability agentic-search-specific | Pass | 3 of 3 | no detail published |
| Listed in MCP registries mcp-registry-listed | Pass | 1 of 1 | no detail published |
| NPM/PyPI SDK package npm-sdk-package | Pass | 1 of 1 | no detail published |
| ChatGPT app listed chatgpt-app-listed | Fail | 0 of 2 | Not found in ChatGPT app directory |
| Registry branding registry-branding | Partial | 1 of 2 | MCP manifest has name and description but no icon at /.well-known/mcp/server-card.json |
| Listed on skills.sh skills-sh-listed | Pass | 1 of 1 | no detail published |
| ARD discovery ard-catalog | Partial | 0 of 1 | /.well-known/ard.json exists but is not valid JSON |
Payments
The agent payment protocols Ora probes for. A site that sells nothing has nothing here, and Ora scores the layer out of zero when none applies.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| UCP - Universal Commerce Protocol ucp-support | Partial | 0 of 3 | no UCP (Universal Commerce Protocol) signals detected |
| ACP - Agentic Commerce Protocol acp-support | Partial | 0 of 3 | no ACP (Agentic Commerce Protocol) signals detected |
| ACP delegate payment acp-delegate-payment | Partial | 0 of 3 | No ACP Delegate Payment signals detected |
| AP2 - Agent Payments Protocol ap2-support | Partial | 0 of 3 | No AP2 (Agent Payments Protocol) signals detected |
| x402 payment protocol x402-support | Partial | 0 of 2 | No x402 payment protocol support detected |
| MPP payment protocol mpp-support | Partial | 0 of 2 | No MPP (Machine Payments Protocol) support detected |
The fixes worth most points
Ora attaches an estimate to each failing or partial check: how many points the site would gain by passing it. These are the 5 with the largest estimates for Sentry, with what Ora observed. The wording of each fix is Ora's; the 28 checks it runs on an MCP server are listed with their layer and tier.
- OpenAPI spec published: fail, 0 of 7, about 3.8 points to gain. Ora saw: No OpenAPI/Swagger specification found
- JSON error responses: fail, 0 of 4, about 2.3 points to gain. Ora saw: API does not return JSON error responses (or no API detected)
- GraphQL typed error model: fail, 0 of 3, about 1.7 points to gain. Ora saw: GraphQL introspection auth-gated and no typed graphql error model documentation found on GraphQL-tagged pages
- ARD discovery: partial, 0 of 1, about 1.6 points to gain. Ora saw: /.well-known/ard.json exists but is not valid JSON
- GraphQL versioning / deprecation policy: fail, 0 of 2, about 1.1 points to gain. Ora saw: GraphQL introspection auth-gated and no graphql versioning / deprecation policy documentation found on GraphQL-tagged pages
Our read
Sentry has done the newer act-layer work and skipped the older: a WebMCP tool is registered in a script bundle, the MCP server at mcp.sentry.dev/mcp answers and requires authentication, it is discoverable at sentry.io/.well-known/mcp.json, OAuth authorization server metadata is on the main domain, @sentry/cli is on npm, SDKs are in four registries, and sentry.io serves an llms.txt and returns markdown on request. The missing piece is an OpenAPI specification, about 4 points, and two published files are broken: the ARD catalog at /.well-known/ard.json is not valid JSON, and the agent skills index has an empty skills array. Endpoints do not answer errors as JSON and the GraphQL introspection is gated. The home page is 15,918 characters at a 4 percent text ratio, just under the target, with two complete Organization blocks. An error-tracking company with two files that would fail its own checks is the sentence the editors could not resist.
Test your own surfaces
The scan above is free and needs no account: enter a domain at ora.ai and read the same four layers for your own site. For an MCP server, Ora scans the server URL itself and runs 28 of its 132 public checks on it, which is why it is the check this directory recommends; the reasons, the limits and the alternatives are on their own page. The command below runs the same audit from a terminal and exits with 1 under the score you set, so it can gate a deploy.
npx ax@0.10 audit https://example.com --min-score 70All 360 checks, one company a day. Corrections to the corrections page.