Rank #1 of 6 in Error Tracking
Showcase


Try itExperimental
See what an agent can do with Sentry before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); the live MCP handshake runs real requests from our edge, right now — including, where the server allows it, one real read-only tool call (bring your own key for auth-gated servers); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -s https://sentry.io/api/0/projects/ # the documented REST API, keyless → auth challengerecorded session — replayed, not liveVerified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Ai debugging — stories about ai debugging in this arenaAi debuggingevidence →
Stories about ai debugging in this arena
Alerting noise — stories about alerting noise in this arenaAlerting noiseevidence →
Stories about alerting noise in this arena
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Data scrubbing — stories about data scrubbing in this arenaData scrubbingevidence →
Stories about data scrubbing in this arena
Error data access — stories about error data access in this arenaError data accessevidence →
Stories about error data access in this arena
Grouping triage — stories about grouping triage in this arenaGrouping triageevidence →
Stories about grouping triage in this arena
Impact analytics — stories about impact analytics in this arenaImpact analyticsevidence →
Stories about impact analytics in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Quotas cost — stories about quotas cost in this arenaQuotas costevidence →
Stories about quotas cost in this arena
Releases regressions — stories about releases regressions in this arenaReleases regressionsevidence →
Stories about releases regressions in this arena
Sdk instrumentation — stories about sdk instrumentation in this arenaSdk instrumentationevidence →
Stories about sdk instrumentation in this arena
Search analytics — stories about search analytics in this arenaSearch analyticsevidence →
Stories about search analytics in this arena
Sourcemaps symbolication — stories about sourcemaps symbolication in this arenaSourcemaps symbolicationevidence →
Stories about sourcemaps symbolication in this arena
Workflow integrations — stories about workflow integrations in this arenaWorkflow integrationsevidence →
Stories about workflow integrations in this arena
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 1 free · 7 paid · 0 enterprise · 30 not stated in evidence
Follow the green: where the map greys out is where Sentry stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓7/10
unlocks → Scoped API keys · Machine-readable spec · Versioning policy · API sandbox · Attach breadcrumbs, custom tags, and user context to every event so a stack trace arrives with the state that produced it · Link an error to Jira, GitHub Issues, or Linear with two-way status sync, so fixing the ticket resolves the error and a regression reopens it
Subscribe to events via webhooks
✓8/10
Build against official SDKs
✓8/10
Issue scoped/least-privilege API credentials for an agent
—–
Connect an agent via an official MCP server
✓8/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
—–
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓9/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
✓7/10
unlocks → MCP client
Operate the product with natural-language commands
✓7/10
Plug MCP servers into this product so it can use their tools
—0/10
Get AI-generated insights and suggestions from my data inside the product
✓8/10
Set up automations that run autonomously in the background
~6/10
Ai debugging — stories about ai debugging in this arenaAi debugging
Stories about ai debugging in this arena
Alerting noise — stories about alerting noise in this arenaAlerting noise
Stories about alerting noise in this arena
Route alerts by project, environment, and severity to Slack, PagerDuty, or email with per-rule thresholds — new issue, frequency spike, affected-user count
✓7/10
Fight alert fatigue with spike protection, per-key rate limits, and mute/ignore rules so one bad deploy doesn't page the whole team all night
~5/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Data scrubbing — stories about data scrubbing in this arenaData scrubbing
Stories about data scrubbing in this arena
Error data access — stories about error data access in this arenaError data access
Stories about error data access in this arena
An agent can pull my top production issues with stack traces via API or MCP, triage them, and file the real bugs into my tracker
~7/10
List, query, and update issues and fetch raw events through a documented REST API with scoped tokens
~5/10
The event-ingestion protocol is documented and open enough that custom clients and compatible SDKs can send events without an official SDK
~4/10
Grouping triage — stories about grouping triage in this arenaGrouping triage
Stories about grouping triage in this arena
Impact analytics — stories about impact analytics in this arenaImpact analytics
Stories about impact analytics in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Quotas cost — stories about quotas cost in this arenaQuotas cost
Stories about quotas cost in this arena
Releases regressions — stories about releases regressions in this arenaReleases regressions
Stories about releases regressions in this arena
I get alerted when an error that was fixed comes back in a newer release, distinct from ordinary new-issue noise
~3/10
Watch release health — crash-free sessions and users, adoption per release — and compare a canary release against the last stable one
—0/10
Associate errors with releases and commits so each issue shows the release it first appeared in and the suspect commit that likely caused it
✓8/10
Sdk instrumentation — stories about sdk instrumentation in this arenaSdk instrumentation
Stories about sdk instrumentation in this arena
Attach breadcrumbs, custom tags, and user context to every event so a stack trace arrives with the state that produced it
—–
Capture native mobile crashes — iOS, Android, NDK — with the device, OS, and app-version context needed to reproduce them
~6/10
Instrument my web frontend, backend services, and mobile apps with official SDKs that capture uncaught errors automatically
✓9/10
Search analytics — stories about search analytics in this arenaSearch analytics
Stories about search analytics in this arena
Sourcemaps symbolication — stories about sourcemaps symbolication in this arenaSourcemaps symbolication
Stories about sourcemaps symbolication in this arena
Workflow integrations — stories about workflow integrations in this arenaWorkflow integrations
Stories about workflow integrations in this arena
Link an error to Jira, GitHub Issues, or Linear with two-way status sync, so fixing the ticket resolves the error and a regression reopens it
—–
The platform connects to my repos so an issue shows suspect commits and code owners, and I can jump from a stack frame to the exact line on my default branch
✓8/10
Sorted by importance (agentic first) (high → low) · 55/55 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | fullpaid | 7/10 | Cclaimed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 7/10 | Tprobed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | fullpaid | 8/10 | Cclaimed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Cclaimed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partialpaid | 6/10 | Cclaimed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | none | untested | none yet | |
Instrument my web frontend, backend services, and mobile apps with official SDKs that capture uncaught errors automatically C Sdk coverage | developer | Sdk instrumentation — stories about sdk instrumentation in this arenaSdk instrumentation | 3 | full | 9/10 | Cclaimed | |
Associate errors with releases and commits so each issue shows the release it first appeared in and the suspect commit that likely caused it C Release tracking | developer | Releases regressions — stories about releases regressions in this arenaReleases regressions | 3 | full | 8/10 | Cclaimed | |
The platform's AI analyzes an issue — stack trace, breadcrumbs, related commits — and proposes a root cause I can act on C Root cause | ai-native user | Ai debugging — stories about ai debugging in this arenaAi debugging | 3 | fullpaid | 8/10 | Cclaimed | |
Upload JavaScript source maps from CI — via CLI or bundler plugin — so production stack traces show my original source, not minified frames C Sourcemaps | developer | Sourcemaps symbolication — stories about sourcemaps symbolication in this arenaSourcemaps symbolication | 3 | full | 8/10 | Tprobed | |
An agent can pull my top production issues with stack traces via API or MCP, triage them, and file the real bugs into my tracker C Agent access | ai-native user | Error data access — stories about error data access in this arenaError data access | 3 | partial | 7/10 | Tprobed | |
Route alerts by project, environment, and severity to Slack, PagerDuty, or email with per-rule thresholds — new issue, frequency spike, affected-user count C Alert routing | sre | Alerting noise — stories about alerting noise in this arenaAlerting noise | 3 | full | 7/10 | Cclaimed | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partialfree | 7/10 | Xcommunity | |
Triage issues — assign an owner, resolve, ignore, or snooze — and the platform reopens a resolved issue automatically when it regresses C Triage | sre | Grouping triage — stories about grouping triage in this arenaGrouping triage | 3 | full | 7/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 6/10 | Cclaimed | |
The platform groups thousands of duplicate events into one issue via stack-trace fingerprinting, and I can customize the grouping when it gets it wrong C Grouping | developer | Grouping triage — stories about grouping triage in this arenaGrouping triage | 3 | partial | 6/10 | Cclaimed | |
List, query, and update issues and fetch raw events through a documented REST API with scoped tokens C Api access | developer | Error data access — stories about error data access in this arenaError data access | 3 | partialpaid | 5/10 | Tprobed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partial | 4/10 | Xcommunity | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
The platform connects to my repos so an issue shows suspect commits and code owners, and I can jump from a stack frame to the exact line on my default branch C Scm context | developer | Workflow integrations — stories about workflow integrations in this arenaWorkflow integrations | 2 | full | 8/10 | Cclaimed | |
The platform's AI can draft a code fix for an error and open a pull request against my repo for human review C Autofix | ai-native user | Ai debugging — stories about ai debugging in this arenaAi debugging | 2 | fullpaid | 8/10 | Cclaimed | |
Upload dSYM, ProGuard, and native debug symbols so mobile and native crashes symbolicate to real function names and lines C Symbolication | developer | Sourcemaps symbolication — stories about sourcemaps symbolication in this arenaSourcemaps symbolication | 2 | full | 8/10 | Tprobed | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | full | 7/10 | Xcommunity | |
Cap event quotas per project and set spend limits so an error storm burns a predictable budget, never a surprise invoice G Quotas | engineering leader | Quotas cost — stories about quotas cost in this arenaQuotas cost | 2 | partial | 6/10 | Cclaimed | |
Capture native mobile crashes — iOS, Android, NDK — with the device, OS, and app-version context needed to reproduce them C Mobile crashes | developer | Sdk instrumentation — stories about sdk instrumentation in this arenaSdk instrumentation | 2 | partial | 6/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 6/10 | Tprobed | |
Scrub PII from error events — server-side scrubbing rules plus SDK-level filtering — before sensitive payloads ever persist C Pii scrubbing | sre | Data scrubbing — stories about data scrubbing in this arenaData scrubbing | 2 | partial | 6/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partialpaid | 5/10 | Tprobed | |
Fight alert fatigue with spike protection, per-key rate limits, and mute/ignore rules so one bad deploy doesn't page the whole team all night C Noise control | sre | Alerting noise — stories about alerting noise in this arenaAlerting noise | 2 | partial | 5/10 | Cclaimed | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | disputed | 5/10 | Dcontradicted | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 4/10 | Cclaimed | |
See error trends across projects and teams on dashboards — top regressions, new issues per release, volume over time C Dashboards | engineering leader | Search analytics — stories about search analytics in this arenaSearch analytics | 2 | partial | 4/10 | Cclaimed | |
The event-ingestion protocol is documented and open enough that custom clients and compatible SDKs can send events without an official SDK C Ingest protocol | developer | Error data access — stories about error data access in this arenaError data access | 2 | partial | 4/10 | Tprobed | |
I get alerted when an error that was fixed comes back in a newer release, distinct from ordinary new-issue noise C Regressions | sre | Releases regressions — stories about releases regressions in this arenaReleases regressions | 2 | partial | 3/10 | Cclaimed | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | 0/10 | ||
Watch release health — crash-free sessions and users, adoption per release — and compare a canary release against the last stable one C Release health | sre | Releases regressions — stories about releases regressions in this arenaReleases regressions | 2 | none | 0/10 | ||
Attach breadcrumbs, custom tags, and user context to every event so a stack trace arrives with the state that produced it C Event context | developer | Sdk instrumentation — stories about sdk instrumentation in this arenaSdk instrumentation | 2 | none | untested | none yet | |
Every issue quantifies real impact — how many users and sessions are affected — so I prioritize by blast radius, not raw event counts C User impact | sre | Impact analytics — stories about impact analytics in this arenaImpact analytics | 2 | none | untested | none yet | |
Link an error to Jira, GitHub Issues, or Linear with two-way status sync, so fixing the ticket resolves the error and a regression reopens it C Issue trackers | developer | Workflow integrations — stories about workflow integrations in this arenaWorkflow integrations | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Search and filter events across projects by tag, release, environment, and custom properties with a real query syntax C Event search | developer | Search analytics — stories about search analytics in this arenaSearch analytics | 2 | none | untested | none yet | |
Merge issues that are really the same bug and split ones the fingerprinter wrongly collapsed C Triage | developer | Grouping triage — stories about grouping triage in this arenaGrouping triage | 1 | partial | 3/10 | Cclaimed | |
Collect user feedback — a crash-report dialog or feedback widget — attached to the exact error event the user hit C User feedback | developer | Impact analytics — stories about impact analytics in this arenaImpact analytics | 1 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 35 stories with headroom
What would move Sentry’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
Evidence shows Sentry ships its own MCP server (mcp.sentry.dev) so other AI assistants can call Sentry's tools, and it can even monitor/observe MCP server traffic (docs-44) — but this is the reverse direction.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
No evidence of any policy, setting, or statement addressing whether user data is used to train AI models (Sentry's own or third-party AI features like Seer/Autofix).
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
The evidence pack shows Sentry's general API access, MCP server, and SAML/SCIM support, but nothing about issuing scoped or least-privilege API credentials specifically for AI agents (e.g., token scopes, agent-specific permission grants).
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
Sentry's docs reference API endpoints (e.g., sentry-docs-23) but there is no evidence of an interactive, runnable API reference (like Swagger/OpenAPI try-it-out); a probe for OpenAPI/Swagger specs returned 404s, suggesting no such interactive tooling is exposed.
Agenticness — how well agents can access and operate the productDownload a machine-readable API spec (OpenAPI or equivalent)
nonemoves API qualityimpact 30
Missing: any linked OpenAPI/Swagger JSON or YAML file, any docs page announcing spec availability.
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
No evidence of a documented API versioning scheme or deprecation policy; the OpenAPI spec probe returned 404s and no docs mention API version numbers or deprecation timelines.
Impact analytics — stories about impact analytics in this arenaEvery issue quantifies real impact — how many users and sessions are affected — so I prioritize by blast radius, not raw event counts
nonemoves PA Scoreimpact 20
The evidence pack covers issue triage, alerts, ownership rules, AI debugging (Seer), and SDK/CLI capabilities, but nothing documents quantifying 'users affected' or 'sessions affected' per issue for blast-radius prioritization.
Automation depth — how much of the product can run unattendedSchedule recurring jobs or workflows
nonemoves PA Scoreimpact 20
Sentry's 'Cron Monitoring' (sentry-docs-35, sentry-docs-50) only tracks the health/uptime of recurring jobs that run elsewhere — it does not let a user actually schedule, define, or execute recurring jobs or AI workflows within Sentry itself.
Showing the top 8 of 35 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map20 surfaces · 39 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Product docs16 stories
- Build against official SDKs
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- The platform's AI can draft a code fix for an error and open a pull request against my repo for human review
- The platform's AI analyzes an issue — stack trace, breadcrumbs, related commits — and proposes a root cause I can act on
- Route alerts by project, environment, and severity to Slack, PagerDuty, or email with per-rule thresholds — new issue, frequency spike, affected-user count
- Fight alert fatigue with spike protection, per-key rate limits, and mute/ignore rules so one bad deploy doesn't page the whole team all night
- Define rules that trigger actions automatically on events
- The platform groups thousands of duplicate events into one issue via stack-trace fingerprinting, and I can customize the grouping when it gets it wrong
- Triage issues — assign an owner, resolve, ignore, or snooze — and the platform reopens a resolved issue automatically when it regresses
- Merge issues that are really the same bug and split ones the fingerprinter wrongly collapsed
- I get alerted when an error that was fixed comes back in a newer release, distinct from ordinary new-issue noise
- Associate errors with releases and commits so each issue shows the release it first appeared in and the suspect commit that likely caused it
- See error trends across projects and teams on dashboards — top regressions, new issues per release, volume over time
- The platform connects to my repos so an issue shows suspect commits and code owners, and I can jump from a stack frame to the exact line on my default branch
CLI docs12 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Set up automations that run autonomously in the background
- Perform bulk operations across many items at once
- The event-ingestion protocol is documented and open enough that custom clients and compatible SDKs can send events without an official SDK
- Export all of my data in open formats and leave
- Associate errors with releases and commits so each issue shows the release it first appeared in and the suspect commit that likely caused it
- Capture native mobile crashes — iOS, Android, NDK — with the device, OS, and app-version context needed to reproduce them
- Upload JavaScript source maps from CI — via CLI or bundler plugin — so production stack traces show my original source, not minified frames
- Upload dSYM, ProGuard, and native debug symbols so mobile and native crashes symbolicate to real function names and lines
- The platform connects to my repos so an issue shows suspect commits and code owners, and I can jump from a stack frame to the exact line on my default branch
Pricing docs10 stories
- Drive the product through a documented public API
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- The platform's AI analyzes an issue — stack trace, breadcrumbs, related commits — and proposes a root cause I can act on
- Route alerts by project, environment, and severity to Slack, PagerDuty, or email with per-rule thresholds — new issue, frequency spike, affected-user count
- List, query, and update issues and fetch raw events through a documented REST API with scoped tokens
- Do everything through the API that I can do in the UI
- Cap event quotas per project and set spend limits so an error storm burns a predictable budget, never a surprise invoice
- See error trends across projects and teams on dashboards — top regressions, new issues per release, volume over time
sentry.io8 stories
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- The platform's AI can draft a code fix for an error and open a pull request against my repo for human review
- The platform's AI analyzes an issue — stack trace, breadcrumbs, related commits — and proposes a root cause I can act on
- An agent can pull my top production issues with stack traces via API or MCP, triage them, and file the real bugs into my tracker
- Do everything through the API that I can do in the UI
- Instrument my web frontend, backend services, and mobile apps with official SDKs that capture uncaught errors automatically
API reference7 stories
- Drive the product through a documented public API
- Perform bulk operations across many items at once
- An agent can pull my top production issues with stack traces via API or MCP, triage them, and file the real bugs into my tracker
- List, query, and update issues and fetch raw events through a documented REST API with scoped tokens
- Triage issues — assign an owner, resolve, ignore, or snooze — and the platform reopens a resolved issue automatically when it regresses
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
Integrations docs7 stories
- Build against official SDKs
- Set up automations that run autonomously in the background
- Operate the product with natural-language commands
- The platform's AI can draft a code fix for an error and open a pull request against my repo for human review
- The platform's AI analyzes an issue — stack trace, breadcrumbs, related commits — and proposes a root cause I can act on
- Define rules that trigger actions automatically on events
- An agent can pull my top production issues with stack traces via API or MCP, triage them, and file the real bugs into my tracker
Platforms docs7 stories
- Run the product headlessly / in CI for automation
- Build against official SDKs
- The event-ingestion protocol is documented and open enough that custom clients and compatible SDKs can send events without an official SDK
- Associate errors with releases and commits so each issue shows the release it first appeared in and the suspect commit that likely caused it
- Capture native mobile crashes — iOS, Android, NDK — with the device, OS, and app-version context needed to reproduce them
- Instrument my web frontend, backend services, and mobile apps with official SDKs that capture uncaught errors automatically
- Upload JavaScript source maps from CI — via CLI or bundler plugin — so production stack traces show my original source, not minified frames
mcp.sentry.dev6 stories
- Connect an agent via an official MCP server
- Build against official SDKs
- Operate the product with natural-language commands
- Perform bulk operations across many items at once
- An agent can pull my top production issues with stack traces via API or MCP, triage them, and file the real bugs into my tracker
- Do everything through the API that I can do in the UI
Hacker News5 stories
docs.sentry.io5 stories
Organization docs5 stories
- Subscribe to events via webhooks
- Route alerts by project, environment, and severity to Slack, PagerDuty, or email with per-rule thresholds — new issue, frequency spike, affected-user count
- Define rules that trigger actions automatically on events
- Choose where my data is stored (region/residency)
- Control data retention and deletion
OpenAPI spec4 stories
- Drive the product through a documented public API
- List, query, and update issues and fetch raw events through a documented REST API with scoped tokens
- The event-ingestion protocol is documented and open enough that custom clients and compatible SDKs can send events without an official SDK
- Do everything through the API that I can do in the UI
Self hosted docs4 stories
AI docs3 stories
Concepts docs3 stories
- Define rules that trigger actions automatically on events
- The platform groups thousands of duplicate events into one issue via stack-trace fingerprinting, and I can customize the grouping when it gets it wrong
- Merge issues that are really the same bug and split ones the fingerprinter wrongly collapsed
Pricing docs3 stories
Changelog docs2 stories
Security legal pii docs2 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -s https://sentry.io/api/0/projects/ # the documented REST API, keyless → auth challengereproduced$ curl -s https://sentry.io/api/0/projects/ # the documented REST API, [redacted]less → auth challenge
{"detail":"Authentication credentials were not provided."}
$curl -sL https://docs.sentry.io/llms.txt | head -4reproduced$ curl -sL https://docs.sentry.io/llms.txt | head -4 # Sentry Documentation > Sentry is a developer-first application monitoring platform that helps developers identify and fix issues in real-time. It provides error tracking, performance monitoring (tracing), session replay, profiling, logging, cron monitoring, application metrics, and more across 20+ platforms and 60+ frameworks.
$curl -si -X POST https://mcp.sentry.dev/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # Sentry's hosted MCP server, keyless → OAuth challengereproduced$ curl -si -X POST https://mcp.sentry.dev/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # Sentry's hosted MCP server, [redacted]less → OAuth challenge HTTP/2 401 www-authenticate: Bearer realm="OAuth", resource_metadata="https://mcp.sentry.dev/.well-known/oauth-protected-resource/mcp"
$curl -s https://raw.githubusercontent.com/getsentry/sentry-api-schema/main/openapi-derefed.json | head -c 200 # the public OpenAPI schemareproduced$ curl -s https://raw.githubusercontent.com/getsentry/sentry-api-schema/main/openapi-derefed.json | head -c 200 # the public OpenAPI schema
{
"openapi": "3.0.3",
"info": {
"title": "API Reference",
"version": "v0",
"description": "Sentry Public API",
"termsOfService": "http://sentry.io/terms/",
"contact": {
"
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
9 of 21 testable claims verified · 0 contradicted → integrity 43/100
29 distinct capability claims found in Sentry’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
9
Verified
12
Unverified
0
Contradicted
17
Undersold
Verified (9)
“A single command configures Claude Code, Cursor, Codex, and Grok to install and set up Sentry”
“Official MCP server lets AI assistants search errors, analyze performance, triage issues, read docs, and manage projects”
“Official MCP server lets AI assistants search errors, analyze performance, triage issues, read docs, and manage projects”
An agent can pull my top production issues with stack traces via API or MCP, triage them, and file the real bugs into my trackerpartialproof ↗
“Manages debug information files (iOS/Android), release/source map management, and code mappings”
Upload dSYM, ProGuard, and native debug symbols so mobile and native crashes symbolicate to real function names and linesfullproof ↗
“Supports uploading JavaScript source maps so stack traces show original source”
Upload JavaScript source maps from CI — via CLI or bundler plugin — so production stack traces show my original source, not minified framesfullproof ↗
“Bulk mutate a list of issues at once”
Perform bulk operations across many items at oncepartialproof ↗
“Can self-host the entire Sentry stack on your own server for free”
“Choice of data storage location (US or EU) for compliance/residency”
Choose where my data is stored (region/residency)fullproof ↗
“API and third-party integrations available on higher-tier plans”
List, query, and update issues and fetch raw events through a documented REST API with scoped tokenspartialproof ↗
Unverified (15)
“SDK integration requires no separate agent installation and adds minimal performance overhead”
Instrument my web frontend, backend services, and mobile apps with official SDKs that capture uncaught errors automaticallyfullproof ↗
“Broad platform/language support — most stacks are already supported”
Instrument my web frontend, backend services, and mobile apps with official SDKs that capture uncaught errors automaticallyfullproof ↗
“Seer AI agent analyzes issues, proposes root causes, and reviews code before merge and after prod deploys”
The platform's AI analyzes an issue — stack trace, breadcrumbs, related commits — and proposes a root cause I can act onfullproof ↗
“AI code review capability flags issues in proposed code changes”
The platform's AI analyzes an issue — stack trace, breadcrumbs, related commits — and proposes a root cause I can act onfullproof ↗
“Autofix feature can generate a fix for a detected issue”
The platform's AI can draft a code fix for an error and open a pull request against my repo for human reviewfullproof ↗
“Fingerprint rules let users customize how events are grouped into issues”
The platform groups thousands of duplicate events into one issue via stack-trace fingerprinting, and I can customize the grouping when it gets it wrongpartialproof ↗
“Associates commits with releases/issues to track which code introduced a bug”
Associate errors with releases and commits so each issue shows the release it first appeared in and the suspect commit that likely caused itfullproof ↗
“Suspect Commits feature identifies likely commits responsible for an issue”
The platform connects to my repos so an issue shows suspect commits and code owners, and I can jump from a stack frame to the exact line on my default branchfullproof ↗
“Ownership rules can auto-assign issue owners based on code ownership”
Triage issues — assign an owner, resolve, ignore, or snooze — and the platform reopens a resolved issue automatically when it regressesfullproof ↗
“Issue status tracking (resolved/ignored/etc.) supports triage workflow”
Triage issues — assign an owner, resolve, ignore, or snooze — and the platform reopens a resolved issue automatically when it regressesfullproof ↗
“Alerting system routes notifications via email, Slack, and PagerDuty”
Route alerts by project, environment, and severity to Slack, PagerDuty, or email with per-rule thresholds — new issue, frequency spike, affected-user countfullproof ↗
“Webhooks available for event notifications”
“Server-side data scrubbing rules remove sensitive data from events before storage”
Scrub PII from error events — server-side scrubbing rules plus SDK-level filtering — before sensitive payloads ever persistpartialproof ↗
“Billing quota management lets teams control usage-based spend”
Cap event quotas per project and set spend limits so an error storm burns a predictable budget, never a surprise invoicepartialproof ↗
“Custom dashboards for visualizing error trends across projects”
See error trends across projects and teams on dashboards — top regressions, new issues per release, volume over timepartialproof ↗
Undersold (17)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Drive the product through a documented public APIfullproof ↗
Get AI-generated insights and suggestions from my data inside the productfullproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Delegate tasks to a built-in AI assistant inside the productfullproof ↗
Operate the product with natural-language commandsfullproof ↗
Fight alert fatigue with spike protection, per-key rate limits, and mute/ignore rules so one bad deploy doesn't page the whole team all nightpartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
The event-ingestion protocol is documented and open enough that custom clients and compatible SDKs can send events without an official SDKpartialproof ↗
Merge issues that are really the same bug and split ones the fingerprinter wrongly collapsedpartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Export all of my data in open formats and leavepartialproof ↗
I get alerted when an error that was fixed comes back in a newer release, distinct from ordinary new-issue noisepartialproof ↗
Capture native mobile crashes — iOS, Android, NDK — with the device, OS, and app-version context needed to reproduce thempartialproof ↗
Claims outside our story set (6)
Real capability claims found in Sentry’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Agent tracing surfaces unexpected AI output, bad tool calls, and spend/performance across agents”
source ↗“SAML and SCIM support for enterprise identity management”
source ↗“Uptime monitoring capability for services”
source ↗“Cron monitoring capability for scheduled job health”
source ↗“Size analysis feature (e.g., app/bundle size tracking)”
source ↗“Session replay capability to review user sessions tied to errors”
source ↗
Business model
Developer plan is free for one user; Team ($26/mo) and Business ($80/mo) bundle prepaid event volume with usage-based on-demand beyond it; Enterprise is custom.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
