Scored by asking 15 questions a buyer of a developer-tools product asks, then grading this site’s own pages: answered, hedged (partial or vague), or silent (no page answers it). How scoring works
15 buyer questions · graded against the site’s own pages
7 of 15 come back answered. 6 get a hedge. 2 meet silence.
confidence high · grounding synthesized · weight 0.00 · Absent
02limits · importance lowGoes silent+7 content pts est.
What is the maximum number of custom tags allowed per event, and is there a character limit on tag key names?
What the pages say
No page on the site addresses this.
The fix
Document the maximum number of custom tags allowed per event and any character limits on tag key names in the Data Management or Size Limits documentation.
confidence high · grounding synthesized · weight 0.00 · Absent
Hedged · 6 of 15 questions
A buyer gets something, then has to guess the rest. Expand any row for the evidence and the fix.
03What's the default outbound rate limit for the JavaScript SDK, and can I override it per client instance?technicalPage missing+3 pts est.+−
What's the default outbound rate limit for the JavaScript SDK, and can I override it per client instance?
What the pages say
The retrieved chunks do not specify a default outbound rate limit for the JavaScript SDK, nor do they document whether it can be overridden per client instance. The chunks do describe server-side rate limit categories such as DSN Limit, Global Limit, and Internal Limit, and note that SDKs may discard events due to "Ratelimit Backoff" or "Queue Overflow".
The fix
Add a dedicated documentation section for JavaScript SDK transport or outbound rate limiting that specifies defaults and per-client instance override options.
04Are Session Replay events deducted from my general error-event quota, or are they billed as a completely separate volume tier?pricingHedges+2 pts est.+−
Are Session Replay events deducted from my general error-event quota, or are they billed as a completely separate volume tier?
What the pages say
The retrieved chunks mention that Session Replay involves an “event quota”—a blog post notes that with sampling on error you’ll have “less anxiety monitoring your event quota”—but they do not specify whether Session Replay events are deducted from your general error-event quota or billed as a completely separate volume tier. The Session Replay product page refers visitors to the pricing page for details.
The fix
Add a clear statement on the Session Replay pricing or FAQ page specifying whether Session Replay consumes the general error-event quota or is billed as a separate volume tier.
confidence medium · grounding synthesized · weight 0.65 · Vague
05What are the guaranteed support response times for Severity-1 incidents on the Business and Enterprise plans?supportPage missing+2 pts est.+−
What are the guaranteed support response times for Severity-1 incidents on the Business and Enterprise plans?
What the pages say
The provided chunks do not specify guaranteed support response times for Severity-1 incidents on the Business or Enterprise plans. The only relevant mention is that Enterprise customers receive a "dedicated support team" (sentry.io/for/enterprise), with no SLA details, severity levels, or Business plan support terms included.
The fix
Create a dedicated Support SLA or Pricing page that explicitly lists guaranteed response times by severity level for each plan tier, including Business and Enterprise.
06Can the Slack integration route alerts to different channels based on custom event tags, or is routing limited to project-level rules only?integrationHedges+2 pts est.+−
Can the Slack integration route alerts to different channels based on custom event tags, or is routing limited to project-level rules only?
What the pages say
Sentry's Slack integration routes alerts primarily through project-level alert rules where you manually select a specific Slack workspace, channel, or user to notify. The documentation also describes Ownership Rules that can route alerts to specific teams and their linked Slack channels. However, while you can optionally include custom event tags in the notification content, none of the retrieved chunks describe routing alerts to different channels based on those event tags.
The fix
Clarify in the Slack alerting documentation whether alert rules support dynamic channel routing based on event tags, or explicitly state that routing is limited to one channel per alert rule plus Ownership Rules.
confidence medium · grounding synthesized · weight 0.65 · Vague
07What is the hard payload size limit for a single error event, and does it differ between SDKs?limitsHedges+2 pts est.+−
What is the hard payload size limit for a single error event, and does it differ between SDKs?
What the pages say
The chunks indicate that error events can be rejected as "Too Large" if they exceed size limits, but they do not specify the exact hard payload size limit for a single error event, instead referring to Sentry's developer documentation for exact limits. The chunks also do not mention whether payload size limits differ between SDKs.
The fix
State the exact hard payload size limit for error events directly in the product docs or stats page, and clarify whether the limit varies by SDK.
confidence medium · grounding synthesized · weight 0.65 · Vague
08If we exceed our monthly profiling hours quota, does profiling data collection stop immediately or does it continue and bill overages?pricingHedges+2 pts est.+−
If we exceed our monthly profiling hours quota, does profiling data collection stop immediately or does it continue and bill overages?
What the pages say
The retrieved chunks do not explicitly state whether profiling data collection stops or continues and bills overages when a monthly profiling hours quota is exceeded. Sentry describes Continuous and UI Profiling as having "transparent billing" based on a unit consumption model where you pay for what you use, but they do not specify overage or hard-stop behavior for profiling hours. For events (not profiling), Sentry offers on-demand capacity with a spending cap, after which additional events are rejected once the cap is reached.
The fix
Add a dedicated FAQ or pricing page note explaining what happens when a customer's monthly profiling hours quota is exceeded—specifically whether data collection stops or overages are billed.
confidence medium · grounding synthesized · weight 0.65 · Vague
What the pages already answer cleanly
7 of 15. Answered with enough specificity for a buyer to act on. This is the bar the queue above is chasing.
pricingAnswered
How many error events are included in the free plan each month, and what happens when I exceed that limit?
What the pages say
The developer plan includes 5,000 errors per month. When the monthly quota is depleted and there is no pay-as-you-go budget left, additional events are discarded due to quota.
confidence high · grounding synthesized · weight 0.95 · Answered
securityAnswered
Will Sentry sign a Business Associate Agreement so we can use it in our HIPAA-compliant environment?
What the pages say
Sentry makes a Business Associate Agreement (BAA) available for customers with subscriptions to eligible plans. The legal page specifies that the BAA is available for Business tier or higher plans to comply with HIPAA. The Terms of Service define the BAA as a separately executed agreement and state that customers on eligible plans who have entered into a BAA with Sentry may submit Protected Health Information (PHI) to the Service.
confidence high · grounding synthesized · weight 0.95 · Answered
integrationAnswered
Does Sentry have a native GitHub Actions integration that automatically ties releases to GitHub deployments?
What the pages say
Yes. Sentry provides the official Sentry Release GitHub Action (`getsentry/action-release`) that automates notifying Sentry of new releases, surfacing suspect commits, and uploading source maps when deploying code via GitHub Actions workflows.
confidence high · grounding stated · weight 1.00 · Answered
migrationAnswered
Does Sentry offer an automated migration path from self-hosted to cloud, or do we have to manually export and re-import all historical data?
What the pages say
Sentry offers a self-serve relocation workflow for moving from self-hosted to SaaS, but it is not a fully automated zero-touch migration. You need owner access and terminal access to your self-hosted instance to generate an encrypted tarball of your configuration data and upload it, and most relocations complete in under an hour. However, historical event data—including issues, events, stack traces, replays, source maps, debug files, and release information—is explicitly not transferred. You do not manually re-import that historical data; new incoming events will begin populating your projects only after you update your DSNs post-relocation.
confidence high · grounding synthesized · weight 0.95 · Answered
technicalAnswered
Does the Next.js SDK automatically instrument both React Server Components and client components, or does each runtime require separate Sentry.init calls?
What the pages say
Each runtime requires separate `Sentry.init` calls in separate initialization files. The Sentry wizard for Next.js creates `instrumentation-client.ts` for the browser (client components), `sentry.server.config.ts` for Node.js server code (which covers React Server Components), and `sentry.edge.config.ts` for edge runtimes. The `instrumentation.ts` file registers the server and edge configurations by conditionally importing the appropriate config based on `process.env.NEXT_RUNTIME`.
confidence high · grounding synthesized · weight 0.95 · Answered
migrationAnswered
Can project alert rules and notification settings be exported via API when migrating from self-hosted, or must they be recreated manually in cloud?
What the pages say
Project alert rules are included in the self-hosted-to-cloud relocation and do not need to be manually recreated, but notification triggers that depend on integrations (e.g., Slack) will be omitted and must be reconfigured. The migration uses a built-in relocation command that generates an encrypted tarball of your data; the chunks do not describe a separate API export for alert rules.
confidence high · grounding synthesized · weight 0.95 · Answered
securityAnswered
Does Sentry's cloud platform support customer-managed encryption keys for data at rest, or is encryption fully provider-controlled?
What the pages say
Sentry's cloud platform uses fully provider-controlled encryption at rest. Sentry states that Google Cloud Platform stores and manages data cryptography keys in its redundant and globally distributed Key Management Service. Customer-managed encryption keys are not mentioned in the retrieved content.
confidence high · grounding stated · weight 1.00 · Answered
Protocol plumbing · 80/10012 of 15 checks pass · each fix +7 protocol pts est.
The other half of the score: 15 checks for the files and headers agents look for. The 3 below are installs, not judgment calls, and most are an afternoon. Expand any for the snippet and the standard it follows. They sit after the queue because none of them changes what your pages say.
Already passing 12 of 15: robots.txt, sitemap.xml, llms.txt, AI crawler access, Content signal, Clean crawl, Markdown negotiation, Server-rendered content, MCP card, Canonical URLs, HTML lang attribute, Organization schema.
Ask this site’s index
Sitedex already serves sentry.io as an MCP endpoint. Ask sentry.io anything an AI agent might ask, and see what its index returns. (To score your own site, use the form below.)
Snippets & configs
For developers and the engineer-on-call: copy these into your tools or your site.
Files from this audit
Built from this crawl. Download or copy each, then install it at the path noted.
llms.txt
Built from this crawl. Install at /llms.txt so agents start here.
organization.json
Organization JSON-LD, pre-filled from this crawl. Wrap in a ld+json script.
server-card.json
MCP server card built from this crawl. Host at /.well-known/mcp/server-card.json.
webmcp.json
WebMCP discovery manifest built from this crawl. Host at /.well-known/webmcp.json.
MCP endpoint
https://mcp.sitedex.dev/s/sentry-io/mcp
The URL anyone's agent points at. Read-only; safe to share.
Claude Code
claude mcp add sentry --transport http https://mcp.sitedex.dev/s/sentry-io/mcp
Drop in <head>. In browsers with WebMCP, this script registers your site's tools with navigator.modelContext.registerTool().
2 · Discovery manifest
{
"schema_version": "2026-04",
"name": "Sentry",
"description": "Sentry is an application monitoring software that helps developers identify and fix errors in their code. WebMCP tools served by Sitedex.",
"homepage": "https://sentry.io",
"documentation": "https://app.sitedex.dev/sites/sentry.io",
"source": "navigator.modelContext",
"tools": [
{
"name": "search_site_content",
"description": "Ask about this site in plain language and get the most relevant passages from its pages, each with the source URL and a relevance score. Searches the site's published text, not live inventory or accounts."
},
{
"name": "get_site_info",
"description": "This site's profile: name, description, category, who it is for, page count, and AI Visibility Score. Use it to learn what the site is before you search it."
},
{
"name": "list_site_pages",
"description": "The pages indexed on this site, with title, URL, and path. Use it to see what the site covers, or to find the path to pass to get_site_page."
},
{
"name": "get_site_page",
"description": "The full markdown of one page on this site, by path. Use it after search_site_content points you at a page and you want all of it."
}
]
}
Host alongside the script at /.well-known/webmcp.json. Crawlers that don't render JS rely on this.
Your turn
See which of these questions your site goes silent on.
Free, about 5 minutes. We crawl your site, test it against the buyer questions your category asks, and name what’s vague, contradictory, or missing, plus the files AI agents look for.
ComingEmbeddable grade badgeScore history and deltasOpt-in public board