Sentry vs Honeybadger

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Sentry
   Sentry✓fullprobed9/10

   A direct probe confirms Sentry serves an llms.txt file at docs.sentry.io/llms.txt with structured documentation content, and Sentry also documents agent-oriented workflows (agents.toml skill dependencies, agent plugin docs, one-command setup for Claude Code/Cursor/Codex/Grok). Missing for 10: independent/community confirmation that an agent successfully consumed the llms.txt or agent-oriented docs end-to-end.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.sentry.io/llms.txt # Sentry Documentation > Sentry is a developer-first application monitoring pla…”
   • [claimed-docs] “One command teaches Claude Code, Cursor, Codex, and Grok how to install and configure Sentry for you.”
   • [claimed-docs] “Whether you're adding Sentry to a new project, debugging a spike in errors, or wiring up alerts, just ask.”
   • [claimed-docs] “It lets you declare agent skill dependencies in agents.toml, lock versions for reproducibility, and ensure every tool on your team discovers…”

   proof ↗⚑ flag

   Honeybadger✓fullprobed8/10

   Honeybadger has a confirmed llms.txt endpoint (HTTP 200) plus dedicated _llms-txt reference docs (product-reference.txt, insights-reference.txt, other-reference.txt) that an agent can be pointed at, and also offers a documented MCP server as an agent-facing integration. missing for 10: independent/hands-on confirmation that an agent actually consumes llms.txt successfully, and no discoverable machine-readable OpenAPI spec to complement it.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.honeybadger.io/llms.txt # Honeybadger.io > Honeybadger provides error tracking, uptime monitoring,…”
   • [claimed-docs] “You can create additional accounts and switch between accounts using the dropdown in the navigation bar.”
   • [claimed-docs] “With it you can specify which fields you want to see, filter the kinds of events that should be returned, perform aggregations and calculati…”
   • [claimed-docs] “Report errors using our [exceptions API](/api/reporting-exceptions/)”
   • [probe] “official MCP server documented at https://docs.honeybadger.io/resources/mcp/”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Honeybadger
   Sentry~partialprobed6/10

   Sentry has a documented CLI (sentry-cli) for sending events, uploading source maps, managing releases, crons, and debug files, which supports CI/headless automation, plus SDKs that integrate into CI/build pipelines. However, evidence is scattered docs-references rather than an explicit 'run Sentry in CI/headlessly' guide or CI integration examples, and no independent hands-on confirmation of CI usage exists. missing for 10: explicit CI/automation guide or pipeline examples, independent verification of headless CI usage, and clarity on which features (Seer, MCP) work outside interactive/agent contexts.

   • [claimed-docs] “It's primarily used for managing debug information files for iOS, Android, release and source maps management, as well as code mappings for …”
   • [claimed-docs] “The sentry-cli tool can also be used for sending events.”
   • [claimed-docs] “It allows you to create, edit and delete releases as well as upload release artifacts for them.”
   • [claimed-docs] “Sentry Crons allows you to monitor the uptime and performance of any scheduled, recurring job.”
   • [probe] “official CLI documented at https://docs.sentry.io/cli/”
   • [claimed-docs] “Uploading Source Maps”

   proof ↗⚑ flag

   Honeybadger✓fullprobed6/10

   Honeybadger ships a CLI and REST API (e.g., `honeybadger deploy`, exceptions/deployments/source-map endpoints) explicitly designed for scripted, non-interactive use, which is exactly what's needed to invoke it headlessly from CI pipelines, and error/deploy tracking runs automatically once configured. Missing for 10: explicit CI/CD integration examples (e.g., GitHub Actions/GitLab CI snippets) and independent hands-on confirmation of CI usage.

   • [claimed-docs] “The Honeybadger CLI provides a Command Line Interface for various Honeybadger-related programs and utilities.”
   • [claimed-docs] “`honeybadger deploy` Notify Honeybadger of deployment”
   • [claimed-docs] “Use this endpoint to notify Honeybadger when a deploy occurs.”
   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”
   • [claimed-docs] “Once our client library is installed and configured, errors thrown by your application are automatically sent to our API.”
   • [probe] “official CLI documented at https://docs.honeybadger.io/lib/ruby/gem-reference/cli/”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Honeybadger
   Sentry✓fullprobed8/10

   Sentry publishes an official MCP server at mcp.sentry.dev enabling AI agents to search errors, analyze performance, triage issues, and manage projects via the Model Context Protocol, corroborated by docs pointing users to set it up alongside the Sentry CLI. Missing for 10: independent/hands-on community verification of the MCP server working in practice, and more detail on setup reliability.

   • [claimed-docs] “Connects AI assistants to Sentry for searching errors, analyzing performance, triaging issues, reading documentation, and managing projects …”
   • [claimed-docs] “Use Sentry without leaving your agent conversations by setting up the Sentry MCP server and Sentry CLI.”
   • [probe] “official MCP server documented at https://mcp.sentry.dev/”
   • [claimed-docs] “One command teaches Claude Code, Cursor, Codex, and Grok how to install and configure Sentry for you.”

   proof ↗⚑ flag

   Honeybadger✓fullprobed9/10

   Honeybadger ships an official hosted MCP server (docs.honeybadger.io/resources/mcp/) that lets an AI assistant connect and gain project management, error investigation, and Insights/BadgerQL query capabilities, with OAuth-based connection flow documented in the changelog. This is first-party documentation of exactly the described capability, though missing for 10: independent/hands-on verification of the MCP server working in practice.

   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “Our hosted MCP server supports OAuth, so you can connect an agent by approving access in your browser instead of copying and pasting a crede…”
   • [claimed-docs] “your AI assistant can fetch Honeybadger data, analyze patterns, and help investigate production issues within your existing workflow.”
   • [probe] “official MCP server documented at https://docs.honeybadger.io/resources/mcp/”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Sentry
   Sentry✓fullprobed8/10

   Sentry ships and documents an official sentry-cli tool (docs.sentry.io/cli) with commands for releases, debug files, sending events, streaming logs, and CI integration, plus a documented flow for AI agents to install/configure Sentry via one command. missing for 10: no independent/hands-on corroboration of CLI use specifically in AI-native/agentic workflows beyond vendor docs.

   • [claimed-docs] “One command teaches Claude Code, Cursor, Codex, and Grok how to install and configure Sentry for you.”
   • [claimed-docs] “It's primarily used for managing debug information files for iOS, Android, release and source maps management, as well as code mappings for …”
   • [claimed-docs] “The sentry-cli tool can also be used for sending events.”
   • [claimed-docs] “The sentry-cli tool can be used to view and stream logs from your Sentry projects.”
   • [claimed-docs] “It allows you to create, edit and delete releases as well as upload release artifacts for them.”
   • [probe] “official CLI documented at https://docs.sentry.io/cli/”

   proof ↗⚑ flag

   Honeybadger✓fullprobed6/10

   Honeybadger ships an official CLI (Ruby gem) documented with commands like `honeybadger deploy` for notifying deployments and other utilities, confirmed by docs and probe. It exists as a first-party tool a script or AI agent could invoke, though it is narrow in scope (deployment notification, limited to Ruby ecosystem) and not marketed as AI-native. Missing for 10: broader multi-language CLI coverage, AI-specific CLI features/flags, and independent/hands-on confirmation of agentic usage.

   • [claimed-docs] “The Honeybadger CLI provides a Command Line Interface for various Honeybadger-related programs and utilities.”
   • [claimed-docs] “`honeybadger deploy` Notify Honeybadger of deployment”
   • [probe] “official CLI documented at https://docs.honeybadger.io/lib/ruby/gem-reference/cli/”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Honeybadger
   Sentry✓fullprobed7/10

   Sentry documents a public REST API (e.g. issue-listing/mutation endpoints) plus a CLI and SDKs that let programmatic/AI-driven clients interact with the platform, and pricing explicitly lists 'API & third-party integrations' as a tier feature. However, probes for a formal OpenAPI/swagger spec all 404'd, so there's no machine-readable schema confirmed, and independent hands-on corroboration of API usage is absent. Missing for 10: a discoverable OpenAPI/swagger spec, independent developer confirmation of API usage.

   • [claimed-docs] “Bulk Mutate a List of Issues”
   • [claimed-docs] “Unlimited users API & third-party integrations 20 custom dashboards Seer: AI debugging agent (subscription required)”
   • [claimed-docs] “It's primarily used for managing debug information files for iOS, Android, release and source maps management, as well as code mappings for …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.sentry.io/openapi.json, https://docs.sentry.io/swagger.json, https://docs.sentry.io/api…”
   • [probe] “official CLI documented at https://docs.sentry.io/cli/”

   proof ↗⚑ flag

   Honeybadger✓fullprobed8/10

   Honeybadger exposes a well-documented public REST API for reporting exceptions, source maps, deployments, and querying faults (docs-15,16,17,19,36), plus a CLI (docs-18,31) and MCP server (docs-13,30) enabling AI agents to interact with it programmatically. No formal OpenAPI/Swagger spec was found via probe, slightly limiting machine-readable discoverability. Missing for 10: a discoverable OpenAPI/Swagger spec and independent third-party confirmation of API robustness.

   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”
   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files. Use the Source Map …”
   • [claimed-docs] “Use this endpoint to notify Honeybadger when a deploy occurs.”
   • [claimed-docs] “Returns a list of faults or a single fault for the given project”
   • [claimed-docs] “The Honeybadger CLI provides a Command Line Interface for various Honeybadger-related programs and utilities.”
   • [claimed-docs] “`honeybadger deploy` Notify Honeybadger of deployment”
   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “your AI assistant can fetch Honeybadger data, analyze patterns, and help investigate production issues within your existing workflow.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.honeybadger.io/openapi.json, https://docs.honeybadger.io/swagger.json, https://docs.hon…”
   • [probe] “official MCP server documented at https://docs.honeybadger.io/resources/mcp/”
   • [probe] “official CLI documented at https://docs.honeybadger.io/lib/ruby/gem-reference/cli/”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Honeybadger
   Sentry—none0/10

   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). No documentation or hands-on evidence addresses credential scoping for agent use.

   ⚑ flag

   Honeybadger~partialprobed3/10

   Honeybadger's hosted MCP server supports OAuth-based approval flows for connecting an agent, which implies some access-control mechanism, but there is no documentation of issuing scoped or least-privilege API keys (e.g., read-only, project-restricted) specifically for agent use. missing for 10: explicit scoped/least-privilege API key creation, granular permission levels for agent credentials, documentation of restricting MCP/agent access to specific resources.

   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “Our hosted MCP server supports OAuth, so you can connect an agent by approving access in your browser instead of copying and pasting a crede…”
   • [probe] “official MCP server documented at https://docs.honeybadger.io/resources/mcp/”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Sentry
   Sentry✓fullprobed8/10

   Sentry documents official SDKs across many languages/platforms (docs-45–49) and explicitly extends these into AI-native workflows via agent tracing/instrumentation docs (docs-42, docs-44), an official MCP server (docs-8, sentry-probe-3), a coding-agent integration guide (docs-41), and one-command setup for Claude Code/Cursor/Codex/Grok (docs-4). This directly supports building against official SDKs in an agentic/AI-native context. Missing for 10: independent/hands-on developer corroboration of AI-native SDK integration specifically, and no explicit versioned SDK API reference cited beyond platform pages.

   • [claimed-docs] “One command teaches Claude Code, Cursor, Codex, and Grok how to install and configure Sentry for you.”
   • [claimed-docs] “Connects AI assistants to Sentry for searching errors, analyzing performance, triaging issues, reading documentation, and managing projects …”
   • [claimed-docs] “Connect an AI coding agent to Sentry so that Seer's root cause analysis can be sent directly to the agent for automated fix generation and p…”
   • [claimed-docs] “automatically collects information about agent runs, tool calls, model interactions, and errors across your entire AI pipeline—from user int…”
   • [claimed-docs] “automatically collect information about MCP server connections, resource access, tool executions, and errors across your entire MCP pipeline”
   • [claimed-docs] “The Sentry team builds and maintains SDKs for most popular languages and frameworks, but there’s also a large ecosystem supported by the com…”
   • [claimed-docs] “we get you up and running with Sentry's Android SDK, automatically reporting errors and exceptions in your application.”
   • [probe] “official MCP server documented at https://mcp.sentry.dev/”

   proof ↗⚑ flag

   Honeybadger~partialprobed6/10

   Honeybadger documents official client libraries/SDKs for multiple languages (Ruby, JS, Elixir/Oban) plus a public reporting/exceptions API, source-map API, and a Ruby CLI, giving AI-native builders concrete integration points (honeybadger-docs-1, -16, -24, -33, -18, -36). However there's no formal OpenAPI/swagger spec (404s on all candidate paths, honeybadger-probe-2) and no consolidated multi-language SDK catalog or independent hands-on confirmation of building against these SDKs. Missing for 10: a machine-readable API spec (OpenAPI), broader documented SDK coverage across major languages, and independent/community validation of SDK integration quality.

   • [claimed-docs] “Once our client library is installed and configured, errors thrown by your application are automatically sent to our API.”
   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files. Use the Source Map …”
   • [claimed-docs] “The Honeybadger CLI provides a Command Line Interface for various Honeybadger-related programs and utilities.”
   • [claimed-docs] “Honeybadger now integrates with Oban (the Python port of the Elixir background job library). With this release you can report unhandled work…”
   • [claimed-docs] “Capture HTTP requests with automatic instrumentation and take advantage of new configuration options for event correlation, event context, h…”
   • [claimed-docs] “Report errors using our [exceptions API](/api/reporting-exceptions/)”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.honeybadger.io/openapi.json, https://docs.honeybadger.io/swagger.json, https://docs.hon…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Sentry
   Sentry✓fullclaimed8/10

   Sentry has a dedicated Webhooks integration-platform doc describing subscribing to events via webhooks, which is a documented first-party capability usable by AI-native/automation consumers alongside its API and MCP surfaces. missing for 10: independent/hands-on corroboration of webhook reliability and no explicit example of an AI agent consuming these webhooks directly.

   • [claimed-docs] “Webhooks”

   proof ↗⚑ flag

   Honeybadger~partialclaimed3/10

   Evidence confirms Honeybadger sends webhook requests (docs-25 mentions 'web hooks' alongside source maps and uptime checks with a secret token header), implying a webhook subscription mechanism exists, but no documentation details how to configure webhook endpoints, which events trigger them, or payload formats. Missing for 10: dedicated webhook setup/configuration docs, list of subscribable event types, payload schema examples, and independent confirmation of reliability.

   • [claimed-docs] “Requests sent from Honeybadger servers for source maps, web hooks, and uptime checks include the header Honeybadger-Token which is a secret …”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Sentry
   Sentry✓fullclaimed8/10

   Sentry ships Seer, an AI debugging agent that performs root-cause analysis, autofix code suggestions, and code review directly within the product (sentry-docs-2, sentry-docs-13, sentry-docs-26, sentry-docs-40), plus agent tracing that surfaces insights on tool calls/spend (sentry-docs-3, sentry-docs-42). This is gated behind a paid subscription and documented mainly via first-party docs/changelog rather than deep independent hands-on validation. Missing for 10: independent/community hands-on verification of Seer's suggestion quality and broader third-party corroboration beyond vendor docs.

   • [claimed-docs] “Catch critical issues before you merge and fix them when they hit prod with Seer, our debugging agent and code reviewer.”
   • [claimed-docs] “Automatically root-cause any issue... Catch critical issues before you merge and fix them when they hit prod with Seer, our debugging agent …”
   • [claimed-docs] “Autofix”
   • [claimed-docs] “Use Autofix to find root causes and generate suggested code fixes for errors and performance issues”
   • [claimed-docs] “Agent tracing helps you catch unexpected output issues, bad tool calls and visualize the spend and performance across all your agents.”
   • [claimed-docs] “automatically collects information about agent runs, tool calls, model interactions, and errors across your entire AI pipeline—from user int…”
   • [claimed-docs] “Seer: AI debugging agent (subscription required)”

   proof ↗⚑ flag

   Honeybadger~partialprobed6/10

   Honeybadger offers AI-adjacent capabilities: natural-language-to-query search ('Describe your search' panel), anomaly detection against learned baselines, and an MCP server that lets an external AI assistant query BadgerQL/Insights data and help investigate issues. However, these are either query-assist/statistical alerting features rather than generative insight/suggestion output embedded directly in the product UI, or they require connecting an external AI agent via MCP rather than native in-product AI-generated insights. missing for 10: evidence of in-app AI-generated summaries/root-cause suggestions surfaced directly in the Honeybadger UI (not via external MCP client), and independent/hands-on validation of the natural-language search or anomaly detection quality.

   • [claimed-docs] “You can search for errors without writing the query yourself. Click the lightbulb icon next to the search box to open the “Describe your sea…”
   • [claimed-docs] “Anomaly detection alerts you when a project’s total error volume deviates from its learned baseline... notifies you when the current rate is…”
   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “your AI assistant can fetch Honeybadger data, analyze patterns, and help investigate production issues within your existing workflow.”
   • [probe] “official MCP server documented at https://docs.honeybadger.io/resources/mcp/”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Sentry
   Sentry~partialclaimed6/10

   Sentry's Seer/Autofix agent autonomously root-causes issues and can even generate PRs via connected coding agents (sentry-docs-2, 13, 26, 40, 41), and alerting/cron monitoring run in the background without manual triggering (sentry-docs-17, 35, 50). However this autonomy is issue-triggered rather than a general-purpose scheduler, gated behind a paid subscription (sentry-docs-59), and there is no independent/hands-on evidence validating how reliably it runs unattended. Missing for 10: independent corroboration of autonomous Seer/Autofix runs, evidence of broader scheduled/background automation beyond issue-triggered debugging, and confirmation it works without subscription.

   • [claimed-docs] “Catch critical issues before you merge and fix them when they hit prod with Seer, our debugging agent and code reviewer.”
   • [claimed-docs] “Automatically root-cause any issue... Catch critical issues before you merge and fix them when they hit prod with Seer, our debugging agent …”
   • [claimed-docs] “Autofix”
   • [claimed-docs] “Use Autofix to find root causes and generate suggested code fixes for errors and performance issues”
   • [claimed-docs] “Connect an AI coding agent to Sentry so that Seer's root cause analysis can be sent directly to the agent for automated fix generation and p…”
   • [claimed-docs] “automatically collects information about agent runs, tool calls, model interactions, and errors across your entire AI pipeline—from user int…”
   • [claimed-docs] “Seer: AI debugging agent (subscription required)”
   • [claimed-docs] “Cron Monitoring”
   • [claimed-docs] “Sentry Crons allows you to monitor the uptime and performance of any scheduled, recurring job.”

   proof ↗⚑ flag

   Honeybadger~partialclaimed5/10

   Honeybadger ships several always-on background automations — Alarms (BadgerQL query + threshold triggers), anomaly detection against a learned baseline, check-ins for cron/scheduled jobs, and uptime monitoring — that run autonomously once configured. However, these are traditional monitoring rules rather than AI-agent-driven automations, and the MCP integration is scoped to investigation/query capabilities rather than configuring or running autonomous background workflows. Missing for 10: evidence that an AI agent can itself create/manage these background automations (e.g. via MCP or API), and any AI-specific autonomous workflow/task runner beyond monitoring alerts.

   • [claimed-docs] “Alarms combine a BadgerQL query (“count all slow requests in the past five minutes”) with a threshold (“when count is > 2”) and trigger aler…”
   • [claimed-docs] “Anomaly detection alerts you when a project’s total error volume deviates from its learned baseline... notifies you when the current rate is…”
   • [claimed-docs] “Check-ins Tracking pings from scheduled tasks and cron jobs”
   • [claimed-docs] “Uptime monitoring Get notified when your API and website are unresponsive”
   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “your AI assistant can fetch Honeybadger data, analyze patterns, and help investigate production issues within your existing workflow.”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Sentry
   Sentry✓fullclaimed7/10

   Sentry ships Seer, a built-in AI debugging agent/code reviewer directly inside the product that can autonomously root-cause issues, suggest fixes, and be delegated tasks like 'just ask' for debugging, alerts, or setup (sentry-docs-2, sentry-docs-26, sentry-docs-39, sentry-docs-40). This is a first-party, in-product AI assistant, not just an external agent connector. Missing for 10: independent/hands-on user corroboration of Seer's actual task-delegation quality, and note that full Seer access requires a paid subscription (sentry-docs-59).

   • [claimed-docs] “Catch critical issues before you merge and fix them when they hit prod with Seer, our debugging agent and code reviewer.”
   • [claimed-docs] “Automatically root-cause any issue... Catch critical issues before you merge and fix them when they hit prod with Seer, our debugging agent …”
   • [claimed-docs] “Autofix”
   • [claimed-docs] “Whether you're adding Sentry to a new project, debugging a spike in errors, or wiring up alerts, just ask.”
   • [claimed-docs] “Use Autofix to find root causes and generate suggested code fixes for errors and performance issues”
   • [claimed-docs] “Seer: AI debugging agent (subscription required)”

   proof ↗⚑ flag

   Honeybadger~partialclaimed3/10

   Honeybadger offers a narrow built-in AI feature — a 'Describe your search' panel that turns natural-language descriptions into BadgerQL queries — but this is a single-purpose assistant, not a general-purpose in-product AI agent you can delegate broader tasks to. The more prominent AI story here (MCP server, docs-13/30) is the reverse direction: it lets an external AI assistant (e.g., Claude) connect to Honeybadger, not a built-in assistant inside Honeybadger itself. Missing for 10: a general-purpose in-app AI assistant capable of multi-step task delegation, evidence of broader assistant capabilities beyond search-query generation, and independent/hands-on corroboration of this feature's usefulness.

   • [claimed-docs] “You can search for errors without writing the query yourself. Click the lightbulb icon next to the search box to open the “Describe your sea…”
   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “your AI assistant can fetch Honeybadger data, analyze patterns, and help investigate production issues within your existing workflow.”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Sentry
   Sentry✓fullprobed7/10

   Sentry ships an official MCP server plus an 'agent plugin' explicitly designed so users can operate Sentry via natural language ('just ask' to add a project, debug errors, or wire up alerts), and the MCP server supports searching errors, triaging issues, and managing projects conversationally. Missing for 10: independent/hands-on user reports confirming natural-language reliability, and no evidence of a native chat/command interface outside the MCP+agent integration path.

   • [claimed-docs] “Whether you're adding Sentry to a new project, debugging a spike in errors, or wiring up alerts, just ask.”
   • [claimed-docs] “Connects AI assistants to Sentry for searching errors, analyzing performance, triaging issues, reading documentation, and managing projects …”
   • [claimed-docs] “Use Sentry without leaving your agent conversations by setting up the Sentry MCP server and Sentry CLI.”
   • [claimed-docs] “Connect an AI coding agent to Sentry so that Seer's root cause analysis can be sent directly to the agent for automated fix generation and p…”
   • [probe] “official MCP server documented at https://mcp.sentry.dev/”

   proof ↗⚑ flag

   Honeybadger~partialprobed6/10

   Honeybadger supports natural-language search via a 'Describe your search' panel that translates plain-language descriptions into BadgerQL queries, and its MCP server lets a connected AI assistant fetch data, run BadgerQL queries, and investigate issues conversationally. However, most core operations (deployments, alarms, integrations, CLI) still rely on structured queries/commands rather than direct natural-language control, and there's no independent evidence of how robust the NL search feature is in practice. Missing for 10: broader native NL command support across all product areas, independent/hands-on validation of NL search accuracy.

   • [claimed-docs] “You can search for errors without writing the query yourself. Click the lightbulb icon next to the search box to open the “Describe your sea…”
   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “your AI assistant can fetch Honeybadger data, analyze patterns, and help investigate production issues within your existing workflow.”
   • [probe] “official MCP server documented at https://docs.honeybadger.io/resources/mcp/”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Sentry—none0/10

   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.

   • [claimed-docs] “Bulk Mutate a List of Issues”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.sentry.io/openapi.json, https://docs.sentry.io/swagger.json, https://docs.sentry.io/api…”

   proof ↗⚑ flag

   Honeybadger—none0/10

   Docs describe static API endpoints (reporting-exceptions, faults, source maps) but there is no evidence of an interactive, runnable API reference/explorer; a probe explicitly found no OpenAPI/Swagger spec at any candidate URL (404s), indicating no such interactive documentation exists.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.honeybadger.io/openapi.json, https://docs.honeybadger.io/swagger.json, https://docs.hon…”
   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”
   • [claimed-docs] “Returns a list of faults or a single fault for the given project”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Sentry—none0/10

   Sentry's docs reference REST API endpoints, but a direct probe for a machine-readable OpenAPI/Swagger spec at the standard docs.sentry.io locations returned 404 for all candidates, and no other evidence pack item shows a downloadable spec file. Missing for 10: any linked OpenAPI/Swagger JSON or YAML file, any docs page announcing spec availability.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.sentry.io/openapi.json, https://docs.sentry.io/swagger.json, https://docs.sentry.io/api…”
   • [claimed-docs] “Bulk Mutate a List of Issues”

   proof ↗⚑ flag

   Honeybadger—none0/10

   The API is documented in prose (endpoints for reporting exceptions, faults, deployments, source maps), but a direct probe for machine-readable OpenAPI/Swagger specs at standard locations returned 404 across all candidates, and no evidence pack item links to a downloadable spec file. missing for 10: an actual OpenAPI/Swagger JSON or YAML file, any documented spec download link, or generator tooling.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.honeybadger.io/openapi.json, https://docs.honeybadger.io/swagger.json, https://docs.hon…”
   • [claimed-docs] “Returns a list of faults or a single fault for the given project”
   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”

   proof ↗⚑ flag

3. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Sentry—none0/10

   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.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.sentry.io/openapi.json, https://docs.sentry.io/swagger.json, https://docs.sentry.io/api…”

   proof ↗⚑ flag

   Honeybadger—none0/10

   Evidence shows a documented REST API (v1/notices, faults, source maps, deployments) but no mention of API versioning scheme or a deprecation policy; the openapi.json probe returned 404s, suggesting no formal API spec is published. No evidence of version headers, changelog of breaking API changes, or deprecation timelines.

   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”
   • [claimed-docs] “Returns a list of faults or a single fault for the given project”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.honeybadger.io/openapi.json, https://docs.honeybadger.io/swagger.json, https://docs.hon…”

   proof ↗⚑ flag

Autofix

1. ai-native userThe platform's AI can draft a code fix for an error and open a pull request against my repo for human review

   weight 2 · round to Sentry
   Sentry✓fullclaimed8/10

   Sentry's Seer/Autofix explicitly generates root-cause analysis and code fixes, and docs describe connecting an AI coding agent so Seer's analysis is sent to the agent for automated fix generation and pull request creation (sentry-docs-41, sentry-docs-40, sentry-docs-26, sentry-docs-13). This is a first-party documented workflow matching the story closely. Missing for 10: independent/hands-on confirmation that PR creation works reliably end-to-end and more detail on human review flow.

   • [claimed-docs] “Connect an AI coding agent to Sentry so that Seer's root cause analysis can be sent directly to the agent for automated fix generation and p…”
   • [claimed-docs] “Use Autofix to find root causes and generate suggested code fixes for errors and performance issues”
   • [claimed-docs] “Autofix”
   • [claimed-docs] “Automatically root-cause any issue... Catch critical issues before you merge and fix them when they hit prod with Seer, our debugging agent …”
   • [claimed-docs] “AI Code Review”

   proof ↗⚑ flag

   Honeybadger—none0/10

   Honeybadger's MCP and integrations let an AI assistant investigate errors and query data, but there is no evidence of it drafting a code fix or opening a pull request against a repo. Missing for 10: any capability or documentation of AI-generated code fixes, automated PR creation, or git-write integration.

   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “your AI assistant can fetch Honeybadger data, analyze patterns, and help investigate production issues within your existing workflow.”
   • [claimed-docs] “We now support detailed issue exports to third-party managers. When enabled, your issue exports to GitHub or GitLab will contain the full ma…”

   proof ↗⚑ flag

Root cause

1. ai-native userThe platform's AI analyzes an issue — stack trace, breadcrumbs, related commits — and proposes a root cause I can act on

   weight 3 · round to Sentry
   Sentry✓fullclaimed8/10

   Sentry's Seer/Autofix explicitly analyzes stack traces, breadcrumbs, and suspect commits to automatically root-cause issues and generate suggested fixes, matching the story closely (sentry-docs-13, sentry-docs-26, sentry-docs-40, sentry-docs-21). This is documented as a first-party feature with a dedicated product page, though gated behind a paid subscription. missing for 10: independent/hands-on validation of root-cause accuracy, and explicit confirmation that breadcrumbs are directly cited in Seer's output (only inferred from feature overlap).

   • [claimed-docs] “Automatically root-cause any issue... Catch critical issues before you merge and fix them when they hit prod with Seer, our debugging agent …”
   • [claimed-docs] “Autofix”
   • [claimed-docs] “Use Autofix to find root causes and generate suggested code fixes for errors and performance issues”
   • [claimed-docs] “Suspect Commits”
   • [claimed-docs] “Seer: AI debugging agent (subscription required)”
   • [claimed-docs] “Connect an AI coding agent to Sentry so that Seer's root cause analysis can be sent directly to the agent for automated fix generation and p…”

   proof ↗⚑ flag

   Honeybadger~partialprobed4/10

   Honeybadger's MCP server lets a connected AI assistant fetch error data, run BadgerQL queries, and 'analyze patterns to help investigate production issues' (docs-13, docs-30), which comes close to AI-driven root-cause analysis. However, this requires the user's own external AI client via MCP rather than a built-in platform AI that automatically correlates stack traces, breadcrumbs, and commits into a proposed root cause — no evidence of an integrated automatic root-cause feature exists. Missing for 10: evidence of a first-party AI feature (not just MCP data access) that ingests stack trace + breadcrumbs + commit history and outputs a concrete root-cause hypothesis, and any hands-on/independent validation of accuracy.

   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “your AI assistant can fetch Honeybadger data, analyze patterns, and help investigate production issues within your existing workflow.”
   • [probe] “official MCP server documented at https://docs.honeybadger.io/resources/mcp/”

   proof ↗⚑ flag

Alert routing

1. sreRoute alerts by project, environment, and severity to Slack, PagerDuty, or email with per-rule thresholds — new issue, frequency spike, affected-user count

   weight 3 · round to Sentry
   Sentry✓fullclaimed7/10

   Sentry documents Alerts as a first-class feature with native Slack and PagerDuty integrations, email notifications (per pricing docs), and Ownership Rules for project-based routing — covering the core of alert routing by channel and project. Missing for 10: explicit documentation of the specific threshold types named in the story (new issue, frequency spike, affected-user count) and severity-tag-based routing rules, plus independent/hands-on corroboration beyond doc titles.

   • [claimed-docs] “Alerts”
   • [claimed-docs] “Slack”
   • [claimed-docs] “PagerDuty”
   • [claimed-docs] “Ownership Rules”
   • [claimed-docs] “One user Error Monitoring and Tracing Alerts and notifications via email 10 custom dashboards MCP access”
   • [claimed-docs] “One user * Error Monitoring and Tracing * Alerts and notifications via email * 10 custom dashboards * MCP access”

   proof ↗⚑ flag

   Honeybadger~partialclaimed6/10

   Honeybadger docs show Slack and PagerDuty integrations, plus 'Alarms' that combine a BadgerQL query with a threshold (e.g., count > N) and anomaly detection for volume spikes, which covers frequency-spike-style alerting and routing to chat/on-call tools. However, there's no evidence of explicit per-project/per-environment routing rules, no documented email alert channel, and no dedicated 'affected-user count' threshold type distinct from generic query-based alarms — missing for 10: environment-based routing rules, email as a routing target, explicit affected-user-count threshold configuration, and severity-tiered rule matrices.

   • [claimed-docs] “Alarms combine a BadgerQL query (“count all slow requests in the past five minutes”) with a threshold (“when count is > 2”) and trigger aler…”
   • [claimed-docs] “Anomaly detection alerts you when a project’s total error volume deviates from its learned baseline... notifies you when the current rate is…”
   • [claimed-docs] “Messages about errors include a button to resolve or reopen the error”
   • [claimed-docs] “You can generate an integration key for Honeybadger by logging in to PagerDuty then clicking on “Add New Service” and choosing “Honeybadger”…”

   proof ↗⚑ flag

Noise control

1. sreFight 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

   weight 2 · round to Sentry
   Sentry~partialclaimed5/10

   Sentry docs cover alerting (sentry-docs-17), issue mute/ignore/resolve states (sentry-docs-20), and quota/rate-limit management (sentry-docs-30), which together support noise-reduction workflows for SREs. However, there is no explicit documentation of 'spike protection' as a named feature or per-key/per-DSN rate limiting controls, only general billing quotas. Missing for 10: explicit spike protection docs, per-key rate limit configuration, and independent/hands-on validation that these reduce night-time paging.

   • [claimed-docs] “Alerts”
   • [claimed-docs] “Issue Status”
   • [claimed-docs] “Billing Quota Management”
   • [claimed-docs] “Ownership Rules”

   proof ↗⚑ flag

   Honeybadger~partialclaimed4/10

   Honeybadger has real alert-fatigue tooling—error deduping/grouping, anomaly detection against a learned baseline, BadgerQL-based alarms with thresholds, and auto-resolve on deploy plus Slack resolve/reopen—but none of the evidence names the specific mechanisms in the story: spike protection, per-key rate limiting, or explicit mute/ignore/snooze rules for notifications. missing for 10: explicit spike-protection throttling, per-key/per-error rate limits, and a documented mute/ignore/snooze feature for alerts.

   • [claimed-docs] “Honeybadger groups identical errors together. Using our navigation bar, you can still navigate between each individual occurrence (or notice…”
   • [claimed-docs] “Alarms combine a BadgerQL query (“count all slow requests in the past five minutes”) with a threshold (“when count is > 2”) and trigger aler…”
   • [claimed-docs] “Anomaly detection alerts you when a project’s total error volume deviates from its learned baseline... notifies you when the current rate is…”
   • [claimed-docs] “Messages about errors include a button to resolve or reopen the error”
   • [claimed-docs] “By default, all unresolved errors are automatically marked as resolved when a deployment is recorded, which helps keep your error list clean…”
   • [claimed-docs] “Deployment tracking lets you record when your app is deployed, see a history of deployments, and correlate code changes with errors. When yo…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Sentry
   Sentry~partialprobed6/10

   Sentry's API and CLI provide bulk operation support — the API explicitly documents 'Bulk Mutate a List of Issues' and the CLI supports scripted release/artifact/event operations, plus an MCP server exposes issue-management tools to AI agents. However, there's no dedicated evidence of AI-native bulk workflows (e.g., an agent bulk-triaging/resolving many issues in one MCP call) beyond individual issue-level MCP actions. Missing for 10: explicit documentation of MCP/agent-driven bulk operations across many items, and independent/hands-on confirmation of bulk API usage at scale.

   • [claimed-docs] “Bulk Mutate a List of Issues”
   • [claimed-docs] “Connects AI assistants to Sentry for searching errors, analyzing performance, triaging issues, reading documentation, and managing projects …”
   • [probe] “official MCP server documented at https://mcp.sentry.dev/”
   • [claimed-docs] “It allows you to create, edit and delete releases as well as upload release artifacts for them.”
   • [claimed-docs] “The sentry-cli tool can also be used for sending events.”

   proof ↗⚑ flag

   Honeybadger~partialclaimed4/10

   There's some evidence of bulk-like operations: deployments automatically mark all unresolved errors as resolved at once (docs-6, docs-29), and BadgerQL/Insights let users run aggregations and calculations across many events (docs-35, docs-8). However, there's no documented UI or API feature for explicit multi-select bulk actions (e.g., bulk resolve/delete/tag many errors at once) beyond the automatic deploy-triggered resolution. Missing for 10: explicit bulk-select UI/API endpoints for mass error management, documented batch operations beyond auto-resolve-on-deploy, independent confirmation of bulk workflows.

   • [claimed-docs] “By default, all unresolved errors are automatically marked as resolved when a deployment is recorded, which helps keep your error list clean…”
   • [claimed-docs] “Deployment tracking lets you record when your app is deployed, see a history of deployments, and correlate code changes with errors. When yo…”
   • [claimed-docs] “With it you can specify which fields you want to see, filter the kinds of events that should be returned, perform aggregations and calculati…”
   • [claimed-docs] “Alarms combine a BadgerQL query (“count all slow requests in the past five minutes”) with a threshold (“when count is > 2”) and trigger aler…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round drawn
   Sentry~partialclaimed6/10

   Sentry supports rule-based automation like Alerts, Ownership Rules, Fingerprint Rules, and Webhooks that trigger notifications/actions (Slack, PagerDuty) on events, plus Autofix/Seer for automated root-cause and PR generation triggered by issues. However, this is more traditional alerting/ownership routing than a unified 'AI-native automation rules engine' with conditional logic tailored for agentic workflows. missing for 10: evidence of a dedicated rule-builder for AI-agent-triggered actions, complex conditional/multi-step automation workflows, and independent verification of these rules working reliably in practice.

   • [claimed-docs] “Alerts”
   • [claimed-docs] “Ownership Rules”
   • [claimed-docs] “Fingerprint Rules”
   • [claimed-docs] “Slack”
   • [claimed-docs] “PagerDuty”
   • [claimed-docs] “Webhooks”
   • [claimed-docs] “Autofix”
   • [claimed-docs] “Connect an AI coding agent to Sentry so that Seer's root cause analysis can be sent directly to the agent for automated fix generation and p…”

   proof ↗⚑ flag

   Honeybadger~partialclaimed6/10

   Honeybadger supports rule-like automation: Alarms combine a BadgerQL query with a threshold to trigger alerts automatically (docs-8), anomaly detection triggers alerts when error volume deviates from baseline (docs-9), and deployments automatically resolve open errors and notify teams (docs-6, docs-29). These qualify as user-defined rules triggering automatic actions on events, but there's no evidence of a general-purpose automation/workflow engine (e.g., custom actions beyond alert/resolve/notify) or that AI-native users can programmatically create these rules via API/CLI/MCP. missing for 10: broader custom-action rule engine, API/CLI/MCP support for creating or managing alarms/anomaly rules, independent verification of rule automation working in practice.

   • [claimed-docs] “Alarms combine a BadgerQL query (“count all slow requests in the past five minutes”) with a threshold (“when count is > 2”) and trigger aler…”
   • [claimed-docs] “Anomaly detection alerts you when a project’s total error volume deviates from its learned baseline... notifies you when the current rate is…”
   • [claimed-docs] “By default, all unresolved errors are automatically marked as resolved when a deployment is recorded, which helps keep your error list clean…”
   • [claimed-docs] “Deployment tracking lets you record when your app is deployed, see a history of deployments, and correlate code changes with errors. When yo…”

   proof ↗⚑ flag

Pii scrubbing

1. sreScrub PII from error events — server-side scrubbing rules plus SDK-level filtering — before sensitive payloads ever persist

   weight 2 · round to Sentry
   Sentry~partialclaimed6/10

   Sentry documents server-side data scrubbing rules (sentry-docs-29) which directly matches the SRE story, and SDK-level filtering (beforeSend/scrubbing hooks) is a known Sentry SDK feature area implied by platform SDK docs, but the evidence pack lacks explicit documentation of SDK-level filtering callbacks or confirmation that scrubbing prevents sensitive payloads from ever persisting server-side (vs. being scrubbed post-ingestion). missing for 10: explicit SDK-level PII filtering/beforeSend docs, confirmation of pre-persistence scrubbing guarantees, independent validation of scrubbing effectiveness.

   • [claimed-docs] “Server-Side Data Scrubbing”

   proof ↗⚑ flag

   Honeybadger—none0/10

   No evidence pack items mention PII scrubbing, data filtering, or SDK-level/server-side redaction rules — none of the docs, changelog, or community items reference this capability at all. missing for 10: server-side scrubbing rule configuration, SDK filter_keys/params filtering, any mention of PII/sensitive data handling before persistence.

   ⚑ flag

Agent access

1. ai-native userAn agent can pull my top production issues with stack traces via API or MCP, triage them, and file the real bugs into my tracker

   weight 3 · round to Sentry
   Sentry~partialprobed7/10

   Sentry ships both an official MCP server (mcp.sentry.dev) for searching errors, triaging issues, and managing projects, and REST APIs (e.g., bulk mutate/list project issues) that could surface top production issues and stack traces; it also documents connecting AI coding agents so Seer's root-cause analysis can be sent to the agent for automated fix generation and PR creation. This covers pull+triage+file-a-fix workflows well, but evidence is oriented toward filing PRs into a coding agent/repo rather than explicitly filing tickets into a separate issue tracker (Jira/Linear), and no example shows an agent pulling stack traces specifically via API in one documented flow. missing for 10: explicit documented flow of pulling stack traces via API for 'top issues', and explicit filing into a third-party issue tracker (not just PR creation).

   • [claimed-docs] “Connects AI assistants to Sentry for searching errors, analyzing performance, triaging issues, reading documentation, and managing projects …”
   • [claimed-docs] “Bulk Mutate a List of Issues”
   • [claimed-docs] “Sentry MCP: fix production issues right from your LLM”
   • [claimed-docs] “Connect an AI coding agent to Sentry so that Seer's root cause analysis can be sent directly to the agent for automated fix generation and p…”
   • [probe] “official MCP server documented at https://mcp.sentry.dev/”

   proof ↗⚑ flag

   Honeybadger~partialprobed6/10

   Honeybadger offers a documented API for fault listing (with stack traces implied via faults/notices) and an official hosted MCP server that lets an AI assistant fetch errors, run BadgerQL queries, and manage projects, which supports pulling and triaging top issues. However, filing bugs into an external tracker is only evidenced via manual GitHub/GitLab/Jira issue export features, not shown as an MCP/agent-driven action, and there's no hands-on/independent proof of the full pull-triage-file workflow via API or MCP. missing for 10: evidence of MCP or API directly creating/filing tickets into external trackers, independent/hands-on confirmation of the end-to-end agent workflow.

   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “Returns a list of faults or a single fault for the given project”
   • [claimed-docs] “your AI assistant can fetch Honeybadger data, analyze patterns, and help investigate production issues within your existing workflow.”
   • [claimed-docs] “We now support detailed issue exports to third-party managers. When enabled, your issue exports to GitHub or GitLab will contain the full ma…”
   • [probe] “official MCP server documented at https://docs.honeybadger.io/resources/mcp/”

   proof ↗⚑ flag

Api access

1. developerList, query, and update issues and fetch raw events through a documented REST API with scoped tokens

   weight 3 · round drawn
   Sentry~partialprobed5/10

   Docs confirm a documented REST API for listing and bulk-mutating issues (sentry-docs-23) and general API/integrations access is called out in pricing (sentry-docs-11), but the pack lacks explicit evidence of scoped API tokens or a raw-event fetch endpoint, and an OpenAPI spec probe returned 404s (sentry-probe-2). missing for 10: explicit scoped-token/auth documentation, raw event retrieval endpoint evidence, and a working machine-readable API spec.

   • [claimed-docs] “Bulk Mutate a List of Issues”
   • [claimed-docs] “Unlimited users API & third-party integrations 20 custom dashboards Seer: AI debugging agent (subscription required)”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.sentry.io/openapi.json, https://docs.sentry.io/swagger.json, https://docs.sentry.io/api…”

   proof ↗⚑ flag

   Honeybadger~partialclaimed5/10

   Honeybadger documents a REST API for faults (issues) with list/single-fault retrieval and search-style querying (docs-19, docs-4), plus a reporting API for creating notices, but there is no evidence of an update-issue endpoint, a raw-events fetch endpoint, or explicit scoped-token support (only a generic API key/Honeybadger-Token is mentioned). missing for 10: documented issue-update endpoint, raw event retrieval endpoint, explicit scoped/read-only token documentation.

   • [claimed-docs] “Returns a list of faults or a single fault for the given project”
   • [claimed-docs] “Example query: `john class:UserError -tag:wip -tag:pending component:"UsersController" action:'update'`.”
   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”
   • [claimed-docs] “Requests sent from Honeybadger servers for source maps, web hooks, and uptime checks include the header Honeybadger-Token which is a secret …”

   proof ↗⚑ flag

Ingest protocol

1. developerThe event-ingestion protocol is documented and open enough that custom clients and compatible SDKs can send events without an official SDK

   weight 2 · round to Honeybadger
   Sentry~partialprobed4/10

   Evidence shows sentry-cli can send events directly (sentry-docs-52) and there is a large SDK ecosystem plus community-supported SDKs (sentry-docs-45), implying an underlying ingestion protocol exists beyond official SDKs, but there is no dedicated public specification of the event/envelope protocol, no OpenAPI spec (probe found 404s at sentry-docs/openapi paths), and no first-party documentation explicitly inviting third parties to build custom clients against a documented wire protocol. missing for 10: a published open protocol/spec for event ingestion (e.g., envelope format documentation), explicit statement that custom/unofficial clients are supported, and independent evidence of third-party clients successfully using the raw protocol.

   • [claimed-docs] “The sentry-cli tool can also be used for sending events.”
   • [claimed-docs] “The Sentry team builds and maintains SDKs for most popular languages and frameworks, but there’s also a large ecosystem supported by the com…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.sentry.io/openapi.json, https://docs.sentry.io/swagger.json, https://docs.sentry.io/api…”

   proof ↗⚑ flag

   Honeybadger✓fullprobed7/10

   Honeybadger documents a plain REST endpoint (POST JSON to https://api.honeybadger.io/v1/notices) for reporting exceptions, plus related endpoints for source maps and deployments, meaning any custom client can integrate without the official SDK. However, there's no formal OpenAPI/schema spec (probe confirms 404s) and no independent evidence of third-party/community SDKs actually built against this raw API. Missing for 10: published OpenAPI/schema definition, independent examples of non-official clients successfully using the ingestion endpoint.

   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”
   • [claimed-docs] “Report errors using our [exceptions API](/api/reporting-exceptions/)”
   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files. Use the Source Map …”
   • [claimed-docs] “Use this endpoint to notify Honeybadger when a deploy occurs.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.honeybadger.io/openapi.json, https://docs.honeybadger.io/swagger.json, https://docs.hon…”

   proof ↗⚑ flag

Grouping

1. developerThe platform groups thousands of duplicate events into one issue via stack-trace fingerprinting, and I can customize the grouping when it gets it wrong

   weight 3 · round to Honeybadger
   Sentry~partialclaimed6/10

   Sentry documents Fingerprint Rules for customizing grouping when automatic stack-trace grouping gets it wrong, and issue-status/triage docs support the workflow. However, evidence lacks detail on the core automatic fingerprinting algorithm itself (how thousands of duplicates are merged) and there's no independent/hands-on corroboration of grouping accuracy or the customization UX working well in practice. Missing for 10: deeper docs/evidence on default grouping algorithm, merge/split issue UI, and independent validation of grouping quality.

   • [claimed-docs] “Fingerprint Rules”
   • [claimed-docs] “Issue Status”
   • [claimed-docs] “Ownership Rules”

   proof ↗⚑ flag

   Honeybadger✓fullcommunity8/10

   Docs confirm automatic grouping of identical errors into a single issue with navigation between occurrences, and explicit customization via error class, component, stack trace, or custom fingerprint; community feedback corroborates satisfaction with deduping. Missing for 10: independent/hands-on evidence of the fingerprinting algorithm's accuracy at scale (thousands of events) and real-world examples of re-grouping mistakes being fixed.

   • [claimed-docs] “You can customize the grouping for each exception by changing the error class name, component, or stack trace—or by sending a custom fingerp…”
   • [claimed-docs] “Honeybadger groups identical errors together. Using our navigation bar, you can still navigate between each individual occurrence (or notice…”
   • [community] “Honeybadger so far. Working well enough. Love the deduping.”

   proof ↗⚑ flag

Triage

1. sreTriage issues — assign an owner, resolve, ignore, or snooze — and the platform reopens a resolved issue automatically when it regresses

   weight 3 · round to Sentry
   Sentry✓fullclaimed7/10

   Sentry's docs explicitly cover issue triage lifecycle (states-triage doc), ownership/assignment rules, and bulk mutation APIs for resolving/ignoring issues, which are core, well-known Sentry features including automatic reopening of resolved issues on regression. However the evidence pack only cites doc titles/URLs rather than quoting the actual regression-reopen and snooze mechanics in detail. Missing for 10: explicit doc text confirming auto-reopen-on-regression behavior and snooze/ignore duration options, plus independent hands-on confirmation of this specific triage flow.

   • [claimed-docs] “Issue Status”
   • [claimed-docs] “Ownership Rules”
   • [claimed-docs] “Bulk Mutate a List of Issues”
   • [claimed-docs] “Suspect Commits”

   proof ↗⚑ flag

   Honeybadger~partialclaimed5/10

   Honeybadger documents resolving and reopening errors (via Slack integration button) and auto-resolving errors on deploy, plus fault listing via API, which covers part of the triage workflow. However, there's no direct evidence of 'assign an owner', 'ignore', or 'snooze' actions, nor confirmation that a resolved issue is automatically reopened when it regresses (only manual reopen via Slack is shown). missing for 10: assign-owner action, ignore action, snooze action, automatic reopening on regression evidence.

   • [claimed-docs] “Messages about errors include a button to resolve or reopen the error”
   • [claimed-docs] “By default, all unresolved errors are automatically marked as resolved when a deployment is recorded, which helps keep your error list clean…”
   • [claimed-docs] “Deployment tracking lets you record when your app is deployed, see a history of deployments, and correlate code changes with errors. When yo…”
   • [claimed-docs] “Returns a list of faults or a single fault for the given project”

   proof ↗⚑ flag

2. developerMerge issues that are really the same bug and split ones the fingerprinter wrongly collapsed

   weight 1 · round to Honeybadger
   Sentry~partialclaimed3/10

   Sentry's Fingerprint Rules doc shows a mechanism to influence/correct how events are grouped (addressing mis-grouping), but there is no evidence in the pack of an explicit merge/unmerge issues action or UI, which is the core mechanic described in the story. Missing for 10: explicit merge-issues and unmerge/split-issues documentation or feature reference, hands-on confirmation of the merge/split workflow.

   • [claimed-docs] “Fingerprint Rules”
   • [claimed-docs] “Issue Status”

   proof ↗⚑ flag

   Honeybadger~partialclaimed5/10

   Honeybadger documents customizable grouping via custom fingerprints, error class, component, or stack trace, which lets developers effectively split incorrectly-collapsed errors into distinct issues [honeybadger-docs-2][honeybadger-docs-3]. However, there is no documented UI or API action for merging two separately-grouped issues back into one bug — the evidence only covers grouping-at-ingestion via fingerprint customization, not a manual merge workflow. Missing for 10: explicit merge-issues feature/API, evidence of an UI 'merge' action, and independent confirmation that fingerprint changes retroactively re-group existing occurrences.

   • [claimed-docs] “You can customize the grouping for each exception by changing the error class name, component, or stack trace—or by sending a custom fingerp…”
   • [claimed-docs] “Honeybadger groups identical errors together. Using our navigation bar, you can still navigate between each individual occurrence (or notice…”
   • [claimed-docs] “Honeybadger provides powerful search features that let you easily find previously-occurred errors by type, location, meta-data and many othe…”

   proof ↗⚑ flag

User feedback

1. developerCollect user feedback — a crash-report dialog or feedback widget — attached to the exact error event the user hit

   weight 1 · round drawn
   Sentry—none0/10

   The evidence pack covers SDKs, error monitoring, tracing, Seer AI, MCP, CLI, and integrations, but contains no mention of a user feedback widget, crash-report dialog, or any mechanism for collecting end-user feedback tied to a specific error event. Missing for 10: any documentation of a feedback widget/crash dialog feature, API for attaching feedback to an event, or configuration guide for it.

   ⚑ flag

   Honeybadger—none0/10

   Honeybadger's evidence covers automatic error capture, grouping, search, deployments, and integrations, but there is no mention of a user-facing crash-report dialog or feedback widget that lets end-users submit feedback tied to a specific error occurrence.

   ⚑ flag

User impact

1. sreEvery issue quantifies real impact — how many users and sessions are affected — so I prioritize by blast radius, not raw event counts

   weight 2 · round drawn
   Sentry—none0/10

   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. Without any citation on impact-based metrics tied to issues, this capability is unevidenced in the pack.

   ⚑ flag

   Honeybadger—none0/10

   Evidence covers error grouping, search, deployments, alarms, and anomaly detection on error volume/rate, but nowhere quantifies user or session impact (e.g., affected-user counts) for prioritization by blast radius. missing for 10: any mention of unique users/sessions affected metric, user-impact scoring, or blast-radius prioritization feature.

   ⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round drawn
   Sentry~partialprobed5/10

   Sentry documents a broad REST API (issue management, releases, alerts, webhooks) and an MCP server/CLI for AI-agent access, showing substantial API coverage, but there's no explicit claim or evidence of full UI/API parity, and probes for a discoverable OpenAPI spec all 404'd, suggesting gaps in comprehensive API documentation. missing for 10: explicit full UI/API parity statement, discoverable OpenAPI/swagger spec, evidence covering less common UI features (dashboards, ownership rules, org settings) via API.

   • [claimed-docs] “Bulk Mutate a List of Issues”
   • [claimed-docs] “Connects AI assistants to Sentry for searching errors, analyzing performance, triaging issues, reading documentation, and managing projects …”
   • [claimed-docs] “Sentry MCP: fix production issues right from your LLM”
   • [claimed-docs] “Unlimited users API & third-party integrations 20 custom dashboards Seer: AI debugging agent (subscription required)”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.sentry.io/openapi.json, https://docs.sentry.io/swagger.json, https://docs.sentry.io/api…”
   • [probe] “official MCP server documented at https://mcp.sentry.dev/”

   proof ↗⚑ flag

   Honeybadger~partialprobed5/10

   Honeybadger exposes a documented REST API for core actions—reporting exceptions, deployments, source maps, and listing faults (honeybadger-docs-15,17,19,28)—plus a CLI and MCP server for agent access (honeybadger-docs-18,13,31). However, the probe found no OpenAPI/swagger spec (honeybadger-probe-2), and many UI-only capabilities (resolving/reopening errors, BadgerQL alarm configuration, team/SAML management, account switching) are not shown to have API equivalents. Missing for 10: comprehensive API parity for error resolution, alarms, account/team management, and a published OpenAPI spec confirming full coverage.

   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”
   • [claimed-docs] “Use this endpoint to notify Honeybadger when a deploy occurs.”
   • [claimed-docs] “Returns a list of faults or a single fault for the given project”
   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files.”
   • [claimed-docs] “The Honeybadger CLI provides a Command Line Interface for various Honeybadger-related programs and utilities.”
   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.honeybadger.io/openapi.json, https://docs.honeybadger.io/swagger.json, https://docs.hon…”
   • [claimed-docs] “You can create additional accounts and switch between accounts using the dropdown in the navigation bar.”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Sentry
   Sentry~partialcommunity4/10

   Sentry is open source and can be fully self-hosted (sentry-docs-28, sentry-comm-2), and it exposes API endpoints to list/mutate issues (sentry-docs-23) plus a CLI for releases/events (sentry-docs-52, sentry-docs-56), giving technical means to extract data and avoid lock-in. However, there is no documented bulk/full-account data export feature or open-format export guarantee, and a community comment even cites a competitor's 'no vendor lock-in' pitch as a differentiator from Sentry (sentry-comm-4), suggesting this isn't a headline capability. Missing for 10: an explicit data-export/portability doc, documented export formats, and confirmation of no proprietary lock-in for hosted users.

   • [claimed-docs] “How you can run all of Sentry on your own server, without paying anything.”
   • [claimed-docs] “Bulk Mutate a List of Issues”
   • [claimed-docs] “The sentry-cli tool can also be used for sending events.”
   • [claimed-docs] “It allows you to create, edit and delete releases as well as upload release artifacts for them.”
   • [community] “I have run the self-hosted version of Sentry for a couple years at my job now and it has worked fantastically... The self-hosted version is …”
   • [community] “I built Cabin as an alternative to Sentry. Less bloat, no vendor lock-in, works with any logger.”

   proof ↗⚑ flag

   Honeybadger~partialclaimed3/10

   Honeybadger exposes a REST API (e.g. list/get faults, reporting exceptions) that returns data in JSON, which could be used to script an export of error data, but there is no documented bulk 'export all your account data' feature, no GDPR-style data-portability tool, and no mention of full account deletion/export workflow. missing for 10: dedicated full-account data export feature, documented open-format bulk export tool, evidence of complete data portability/leave workflow.

   • [claimed-docs] “Returns a list of faults or a single fault for the given project”
   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”
   • [claimed-docs] “We now support detailed issue exports to third-party managers. When enabled, your issue exports to GitHub or GitLab will contain the full ma…”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Sentry
   Sentry!disputedcontradicted5/10

   Sentry's source is publicly visible on GitHub (sentry-gh-1, sentry-gh-2) and self-hosting docs (sentry-docs-28) reference running 'all of Sentry' for free, with community praise for the 'fully open source nature' (sentry-comm-1). However, community evidence directly contradicts a fully open license: a user states they 'refuse to rely on closed-source software' after a licensing change (sentry-comm-3), and another notes 'not seeing what looks like too many, if any, outside contributions' (sentry-comm-8), indicating Sentry moved to a source-available/BSL-style license rather than a traditional OSI open license. Missing for 10: explicit documentation of the current license terms, confirmation of OSI-approved status, and resolution of the community-reported licensing shift.

   • [github] “Sentry is the debugging platform that helps every developer detect, trace, and fix issues.”
   • [github] “Sentry is the debugging platform that helps every developer detect, trace, and fix issues. Code breaks, fix it faster.”
   • [claimed-docs] “How you can run all of Sentry on your own server, without paying anything.”
   • [community] “We're huge fans of Sentry and have it deeply integrated in our products. The fully open source nature has helped us a ton with these advance…”
   • [community] “This is a very disappointing development. I was hoping to implement Sentry for a side project I have been working on, now I will have to fin…”
   • [community] “I know for a fact that your competition is using your code, even where they've built a differentiated service, e.g. Embrace is using Sentry …”

   proof ↗⚑ flag

   Honeybadger—none0/10

   Honeybadger is a closed, commercial SaaS product; no evidence in the pack indicates its source code is published under an open license (client libraries being open-source is not addressed, and the core service is proprietary). Missing for 10: any mention of an open-source license, public source repository, or licensing terms.

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Sentry
   Sentry~partialcommunity7/10

   Sentry officially documents running the full core product self-hosted for free (sentry-docs-28, sentry-docs-9), and community reports confirm it works well long-term (sentry-comm-2). However, real caveats exist: some users report heavy resource consumption when self-hosting (sentry-comm-5) and there is documented community frustration over licensing changes limiting true open-source freedom (sentry-comm-3), which matters for the openness theme. Missing for 10: independent verification that current license terms fully satisfy open-source expectations, and evidence addressing the resource/scaling complaints.

   • [claimed-docs] “How you can run all of Sentry on your own server, without paying anything.”
   • [claimed-docs] “Sentry offers and maintains a minimal setup that works out-of-the-box for simple use cases.”
   • [community] “I have run the self-hosted version of Sentry for a couple years at my job now and it has worked fantastically... The self-hosted version is …”
   • [community] “Each release would unleash more containers and consume more memory until we couldn't run anything on the 32gb server except Sentry.”
   • [community] “This is a very disappointing development. I was hoping to implement Sentry for a side project I have been working on, now I will have to fin…”

   proof ↗⚑ flag

   Honeybadger—none0/10

   Honeybadger is presented as a hosted SaaS product (api.honeybadger.io) with no evidence of an open-source self-hosted core, on-premise deployment option, or Docker/self-host installation guide anywhere in the evidence pack.

   ⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to Sentry
   Sentry✓fullcommunity7/10

   Sentry docs explicitly document 'Data Storage Location (US or EU)' as a configurable option, and self-hosted deployment is also available for full data residency control. Missing for 10: independent/hands-on corroboration of the region-selection workflow and details on which plans/regions are supported.

   • [claimed-docs] “Data Storage Location (US or EU)”
   • [claimed-docs] “How you can run all of Sentry on your own server, without paying anything.”
   • [community] “I have run the self-hosted version of Sentry for a couple years at my job now and it has worked fantastically... The self-hosted version is …”

   proof ↗⚑ flag

   Honeybadger—none0/10

   No evidence in the pack addresses data residency, regional hosting options, or ability to choose where data is stored; only data retention (Insights replication) and security token handling are mentioned. missing for 10: any mention of region selection, EU/US hosting options, or data residency controls.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Sentry—none0/10

   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). Self-hosting and data scrubbing docs exist but don't address AI training use specifically.

   ⚑ flag

   Honeybadger—none0/10

   No evidence in the pack addresses AI training data usage or opt-out policies for Honeybadger's data; the product is an error-tracking/monitoring tool and this axis is plausible (e.g., a privacy policy statement about AI training) but nothing documents it. Missing for 10: any privacy policy statement on AI training data usage, opt-out mechanism, or data processing terms addressing AI model training.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Sentry
   Sentry~partialclaimed4/10

   Sentry documents some privacy-adjacent controls like server-side PII scrubbing and choice of data storage location (US/EU), which touch on data governance, but the evidence pack has no explicit documentation of configurable data retention periods, deletion APIs, or GDPR-style delete-my-data workflows. Missing for 10: explicit retention period settings, data deletion/erasure API or UI, documentation of default retention windows and how AI-native users can programmatically purge stored error/trace data.

   • [claimed-docs] “Server-Side Data Scrubbing”
   • [claimed-docs] “Data Storage Location (US or EU)”
   • [claimed-docs] “Billing Quota Management”

   proof ↗⚑ flag

   Honeybadger—none0/10

   Evidence only hints that Business/Enterprise accounts can replicate Insights data for longer retention (docs-22), but there is no mention of any user-facing control to configure retention windows, purge/delete data on demand, or comply with deletion requests. Missing for 10: documented retention settings, a data-deletion API/UI, and any GDPR-style erasure mechanism.

   • [claimed-docs] “If you need to keep your Insights data longer than Honeybadger stores it, Business and Enterprise accounts can now replicate”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Sentry—none0/10

   No evidence pack items address telemetry/usage-tracking opt-out settings for Sentry itself (e.g., product analytics or CLI telemetry opt-out flags); only data scrubbing and self-hosted options are mentioned, which is a different concern than telemetry opt-out.

   ⚑ flag

   Honeybadger—none0/10

   Honeybadger itself is an error-tracking/telemetry product whose core function is collecting data from customer apps; the evidence pack contains no mention of an opt-out mechanism for telemetry/usage tracking related to the AI assistant/MCP integration or the product's own data collection practices. Since this axis (opting out of tracking) is a fair privacy-posture question for an AI-native user of any product, but no evidence shows such an opt-out exists, the verdict is none. Missing for 10: any documentation of an opt-out/telemetry-disable setting, privacy controls for AI assistant usage data, or opt-out options for the MCP integration.

   ⚑ flag

Quotas

1. engineering leaderCap event quotas per project and set spend limits so an error storm burns a predictable budget, never a surprise invoice

   weight 2 · round to Sentry
   Sentry~partialclaimed6/10

   Sentry documents 'Billing Quota Management' and 'Advanced quota management' as pricing-tier features, indicating per-project event quotas and spend controls exist, but the evidence pack lacks detail on how spend caps are configured, alerting on quota thresholds, or hard-stop billing guarantees. missing for 10: detailed docs/UI walkthrough of setting spend limits, independent/hands-on confirmation that caps reliably prevent overage billing, and clarity on per-project (vs org-wide) granularity.

   • [claimed-docs] “Billing Quota Management”
   • [claimed-docs] “Advanced quota management”

   proof ↗⚑ flag

   Honeybadger—none0/10

   No evidence anywhere in the pack of event quota caps, spend/budget limits, or usage-based throttling controls for a project; the evidence covers error grouping, search, deployments, alarms, and MCP/CLI integrations but nothing about cost or quota governance.

   ⚑ flag

Regressions

1. sreI get alerted when an error that was fixed comes back in a newer release, distinct from ordinary new-issue noise

   weight 2 · round to Honeybadger
   Sentry~partialclaimed3/10

   Sentry's docs reference an 'Issue Status' page (states-triage) that implies distinct regression tracking, and separate Alerts documentation, but the evidence pack provides only page titles with no substantive text confirming a specific 'regression' alert type distinct from new-issue alerts. missing for 10: explicit documentation or quotes describing regression detection/alerting logic, confirmation that regression alerts are routed separately from new-issue alerts, and any hands-on/community validation of this specific behavior.

   • [claimed-docs] “Issue Status”
   • [claimed-docs] “Alerts”
   • [claimed-docs] “Associate Commits”

   proof ↗⚑ flag

   Honeybadger~partialclaimed5/10

   Honeybadger auto-resolves errors on deploy and tracks reoccurrences (doc-6, doc-29), and Slack messages include a 'resolve or reopen' button implying errors can reopen (doc-10), which is the mechanical basis for detecting a fixed error's return. However, there is no explicit evidence of a distinct 'regression' alert type or notification that flags a reopened error differently from a brand-new issue, so SREs would have to infer regressions from reopen state rather than get a dedicated alert. Missing for 10: explicit regression-specific alert/notification distinct from new-issue alerts, and confirmation that reopening a resolved error triggers a notification at all.

   • [claimed-docs] “By default, all unresolved errors are automatically marked as resolved when a deployment is recorded, which helps keep your error list clean…”
   • [claimed-docs] “Deployment tracking lets you record when your app is deployed, see a history of deployments, and correlate code changes with errors. When yo…”
   • [claimed-docs] “Messages about errors include a button to resolve or reopen the error”
   • [claimed-docs] “`occurred.after:'last deploy'` Errors that occurred since the most recent deployment”

   proof ↗⚑ flag

Release health

1. sreWatch release health — crash-free sessions and users, adoption per release — and compare a canary release against the last stable one

   weight 2 · round drawn
   Sentry—none0/10

   The evidence pack includes only generic release docs (Associate Commits, releases.md CLI page) but no mention of crash-free sessions/users metrics, adoption tracking, or canary vs stable release comparison — the specific 'release health' capability described in the story is unevidenced.

   • [claimed-docs] “Associate Commits”
   • [claimed-docs] “It allows you to create, edit and delete releases as well as upload release artifacts for them.”

   proof ↗⚑ flag

   Honeybadger—none0/10

   Honeybadger documents deployment tracking (correlating errors with deploys, diffing against last deploy, auto-resolving errors on deploy) but there is no evidence of crash-free sessions/users metrics or per-release adoption percentages, which are the specific release-health metrics this story asks about.

   • [claimed-docs] “By default, all unresolved errors are automatically marked as resolved when a deployment is recorded, which helps keep your error list clean…”
   • [claimed-docs] “When GitHub or GitLab is connected, Honeybadger links the revision to a comparison page that shows a diff of what changed since the last dep…”
   • [claimed-docs] “Use this endpoint to notify Honeybadger when a deploy occurs.”
   • [claimed-docs] “`occurred.after:'last deploy'` Errors that occurred since the most recent deployment”
   • [claimed-docs] “Deployment tracking lets you record when your app is deployed, see a history of deployments, and correlate code changes with errors. When yo…”

   proof ↗⚑ flag

Release tracking

1. developerAssociate errors with releases and commits so each issue shows the release it first appeared in and the suspect commit that likely caused it

   weight 3 · round to Sentry
   Sentry✓fullclaimed8/10

   Sentry docs explicitly cover 'Associate Commits' and 'Suspect Commits' features tying issues to releases and the likely-causing commit, backed by supporting infra like source maps, code mappings, and CLI release/commit association tooling. Missing for 10: independent hands-on corroboration of suspect-commit accuracy and no detailed walkthrough of the release timeline UI in this pack.

   • [claimed-docs] “Associate Commits”
   • [claimed-docs] “Suspect Commits”
   • [claimed-docs] “Code mappings link stack trace paths to source code paths in your repository. They enable features like source context, suspect commits, sta…”
   • [claimed-docs] “It allows you to create, edit and delete releases as well as upload release artifacts for them.”
   • [claimed-docs] “Uploading Source Maps”

   proof ↗⚑ flag

   Honeybadger~partialclaimed5/10

   Honeybadger's deployment tracking records deploys, auto-resolves errors on deploy, and (with GitHub/GitLab connected) links a revision to a diff of what changed since the last deploy, plus supports queries like 'occurred.after:last deploy' to correlate errors with releases. However, there's no documented evidence of a per-issue 'first seen in release X' badge or automatic 'suspect commit' attribution pinpointing which commit likely caused a specific error, which is the core of this story. Missing for 10: explicit per-error 'first appeared in release' metadata, automated suspect-commit/blame attribution shown on the issue itself, independent corroboration of this workflow.

   • [claimed-docs] “By default, all unresolved errors are automatically marked as resolved when a deployment is recorded, which helps keep your error list clean…”
   • [claimed-docs] “When GitHub or GitLab is connected, Honeybadger links the revision to a comparison page that shows a diff of what changed since the last dep…”
   • [claimed-docs] “`occurred.after:'last deploy'` Errors that occurred since the most recent deployment”
   • [claimed-docs] “Deployment tracking lets you record when your app is deployed, see a history of deployments, and correlate code changes with errors. When yo…”

   proof ↗⚑ flag

Event context

1. developerAttach breadcrumbs, custom tags, and user context to every event so a stack trace arrives with the state that produced it

   weight 2 · round to Honeybadger
   Sentry—none0/10

   The evidence pack confirms Sentry SDKs exist and capture errors/traces (e.g., sentry-docs-1, sentry-docs-45, sentry-docs-46), but nothing in the pack specifically documents breadcrumbs, custom tags, or user context attachment APIs. Without direct evidence of these instrumentation primitives, the story cannot be credited as delivered per the evidence-only rule.

   ⚑ flag

   Honeybadger~partialclaimed4/10

   Evidence shows tag-based search syntax (implying tags can be attached) and a changelog note about 'event context' and 'event correlation' configuration in JS packages, but there is no explicit documentation of breadcrumb trails or explicit user-context attachment on error notices. missing for 10: explicit breadcrumb API/docs, explicit user context attachment API, worked example showing tags+context+breadcrumbs together on a single event.

   • [claimed-docs] “Example query: `john class:UserError -tag:wip -tag:pending component:"UsersController" action:'update'`.”
   • [claimed-docs] “Capture HTTP requests with automatic instrumentation and take advantage of new configuration options for event correlation, event context, h…”
   • [claimed-docs] “You can customize the grouping for each exception by changing the error class name, component, or stack trace—or by sending a custom fingerp…”

   proof ↗⚑ flag

Mobile crashes

1. developerCapture native mobile crashes — iOS, Android, NDK — with the device, OS, and app-version context needed to reproduce them

   weight 2 · round to Sentry
   Sentry~partialclaimed6/10

   Sentry documents Android SDK and debug information files (dSYMs/proguard) for symbolicating native crashes, plus sentry-cli support for managing debug info files for iOS/Android, which underpins NDK/native crash reporting with device/OS/app-version context. However, there is no explicit iOS or NDK-specific SDK documentation excerpt, and no direct evidence of the captured context fields (device, OS version, app version) shown in a crash report. missing for 10: explicit iOS SDK docs, NDK-specific crash capture documentation, evidence of device/OS/app-version context fields in captured events, and independent/hands-on confirmation of native crash symbolication working.

   • [claimed-docs] “we get you up and running with Sentry's Android SDK, automatically reporting errors and exceptions in your application.”
   • [claimed-docs] “Debug information files allow Sentry to extract stack traces and provide more information about crash reports for most compiled platforms.”
   • [claimed-docs] “It's primarily used for managing debug information files for iOS, Android, release and source maps management, as well as code mappings for …”
   • [claimed-docs] “It’s primarily used for managing debug information files for iOS, Android, release and source maps management, as well as code mappings for …”

   proof ↗⚑ flag

   Honeybadger—none0/10

   Evidence pack covers Ruby, JS, and general error-reporting APIs, deployments, integrations, and MCP/CLI tooling, but contains no mention of iOS, Android, or NDK SDKs, or native mobile crash context (device, OS, app version). Missing for 10: iOS SDK docs, Android SDK docs, NDK/native crash capture, mobile device/app-version context capture.

   • [claimed-docs] “Once our client library is installed and configured, errors thrown by your application are automatically sent to our API.”
   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”
   • [claimed-docs] “Capture HTTP requests with automatic instrumentation and take advantage of new configuration options for event correlation, event context, h…”

   proof ↗⚑ flag

Sdk coverage

1. developerInstrument my web frontend, backend services, and mobile apps with official SDKs that capture uncaught errors automatically

   weight 3 · round to Sentry
   Sentry✓fullclaimed9/10

   Sentry documents SDKs for a broad range of platforms (Android, .NET, Elixir, Dart, JavaScript, etc.) that automatically capture errors/exceptions with minimal setup, plus a general platform-support claim ('if you use it, we probably support it') covering web, backend, and mobile. Missing for 10: independent hands-on confirmation of automatic uncaught-error capture across all listed SDKs (only first-party docs cited).

   • [claimed-docs] “Drop in the SDK. No agents to install. No performance surprises.”
   • [claimed-docs] “If you use it, we probably support it.”
   • [claimed-docs] “The Sentry team builds and maintains SDKs for most popular languages and frameworks, but there’s also a large ecosystem supported by the com…”
   • [claimed-docs] “we get you up and running with Sentry's Android SDK, automatically reporting errors and exceptions in your application.”
   • [claimed-docs] “Sentry's Elixir SDK enables automatic reporting of errors, exceptions and messages. You can also use it to monitor your cron jobs.”
   • [claimed-docs] “capture your first errors and traces, and view them in Sentry”
   • [claimed-docs] “you can monitor interactions between multiple services or applications by enabling tracing... You can also collect and analyze performance p…”
   • [claimed-docs] “Monitor in five lines... Drop in the SDK. No agents to install. No performance surprises.”

   proof ↗⚑ flag

   Honeybadger~partialclaimed6/10

   Docs confirm automatic uncaught-error capture via client libraries ("errors thrown by your application are automatically sent to our API"), JS/frontend automatic instrumentation and source-map support, and a generic exceptions API for backend reporting. However, the evidence pack lacks explicit confirmation of dedicated mobile SDKs (iOS/Android) or a list of officially supported backend languages beyond the Ruby CLI/gem reference, so mobile coverage is unconfirmed. Missing for 10: explicit mobile SDK documentation, multi-language backend SDK list, independent hands-on verification of auto-capture across platforms.

   • [claimed-docs] “Once our client library is installed and configured, errors thrown by your application are automatically sent to our API.”
   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files. Use the Source Map …”
   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files.”
   • [claimed-docs] “Capture HTTP requests with automatic instrumentation and take advantage of new configuration options for event correlation, event context, h…”
   • [claimed-docs] “Report errors using our [exceptions API](/api/reporting-exceptions/)”
   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”

   proof ↗⚑ flag

Dashboards

1. engineering leaderSee error trends across projects and teams on dashboards — top regressions, new issues per release, volume over time

   weight 2 · round to Honeybadger
   Sentry~partialclaimed4/10

   Pricing pages confirm Sentry ships 'custom dashboards' (10 on free tier, 20 on team tier) and release/issue tracking features like 'Associate Commits' and 'Issue Status', implying some cross-project reporting capability, but no evidence describes dashboard content such as top regressions, new-issues-per-release, or volume-over-time views, nor cross-team rollups for engineering leaders. Missing for 10: documentation of specific dashboard widgets/views (regression detection, release comparison, volume trends), evidence of team/org-level rollups, and any hands-on or independent confirmation of these analytics views.

   • [claimed-docs] “One user Error Monitoring and Tracing Alerts and notifications via email 10 custom dashboards MCP access”
   • [claimed-docs] “Unlimited users API & third-party integrations 20 custom dashboards Seer: AI debugging agent (subscription required)”
   • [claimed-docs] “Associate Commits”
   • [claimed-docs] “Issue Status”
   • [claimed-docs] “One user * Error Monitoring and Tracing * Alerts and notifications via email * 10 custom dashboards * MCP access”

   proof ↗⚑ flag

   Honeybadger~partialclaimed6/10

   Honeybadger's BadgerQL/Insights, deployment tracking (correlating errors with releases, 'occurred.after:last deploy' queries), and anomaly detection support volume-over-time and per-release regression tracking, giving engineering leaders solid analytics tools. However, evidence never shows a native cross-project/cross-team rollup dashboard — only per-account switching (docs-34) — so the 'across projects and teams' aggregation aspect of the story is unproven. Missing for 10: explicit cross-project/team aggregated dashboard UI, named 'top regressions' report, and independent/hands-on confirmation of dashboard usability at leadership level.

   • [claimed-docs] “Alarms combine a BadgerQL query (“count all slow requests in the past five minutes”) with a threshold (“when count is > 2”) and trigger aler…”
   • [claimed-docs] “Anomaly detection alerts you when a project’s total error volume deviates from its learned baseline... notifies you when the current rate is…”
   • [claimed-docs] “`occurred.after:'last deploy'` Errors that occurred since the most recent deployment”
   • [claimed-docs] “Deployment tracking lets you record when your app is deployed, see a history of deployments, and correlate code changes with errors. When yo…”
   • [claimed-docs] “Honeybadger provides powerful search features that let you easily find previously-occurred errors by type, location, meta-data and many othe…”
   • [claimed-docs] “With it you can specify which fields you want to see, filter the kinds of events that should be returned, perform aggregations and calculati…”
   • [claimed-docs] “You can create additional accounts and switch between accounts using the dropdown in the navigation bar.”

   proof ↗⚑ flag

Event search

1. developerSearch and filter events across projects by tag, release, environment, and custom properties with a real query syntax

   weight 2 · round to Honeybadger
   Sentry—none0/10

   The evidence pack contains no documentation or claims about Sentry's issue search/query syntax (e.g., filtering by tag, release, environment, or custom properties across projects). Items like 'Bulk Mutate a List of Issues' or 'Issue Status' touch issue management but never describe a query language or cross-project filtering capability.

   ⚑ flag

   Honeybadger✓fullclaimed8/10

   Honeybadger documents a real BadgerQL-style query syntax (tag:, class:, component:, action:, occurred.after: 'last deploy', negation with -tag:) for filtering errors/events by tag, release/deploy, environment-like properties and custom fields, plus a natural-language-to-query assist feature and Insights query capabilities for aggregation/filtering across fields. missing for 10: explicit documentation of cross-project search/filtering (queries appear scoped per-project) and independent hands-on validation of the query syntax's breadth beyond docs.

   • [claimed-docs] “Example query: `john class:UserError -tag:wip -tag:pending component:"UsersController" action:'update'`.”
   • [claimed-docs] “You can search for errors without writing the query yourself. Click the lightbulb icon next to the search box to open the “Describe your sea…”
   • [claimed-docs] “`occurred.after:'last deploy'` Errors that occurred since the most recent deployment”
   • [claimed-docs] “Honeybadger provides powerful search features that let you easily find previously-occurred errors by type, location, meta-data and many othe…”
   • [claimed-docs] “Honeybadger's error search and BadgerQL can answer almost any question about your e”
   • [claimed-docs] “With it you can specify which fields you want to see, filter the kinds of events that should be returned, perform aggregations and calculati…”

   proof ↗⚑ flag

Sourcemaps

1. developerUpload JavaScript source maps from CI — via CLI or bundler plugin — so production stack traces show my original source, not minified frames

   weight 3 · round to Sentry
   Sentry✓fullprobed8/10

   Sentry docs explicitly cover uploading JavaScript source maps (sentry-docs-15), sentry-cli's role in release/source map management and code mappings (sentry-docs-6, sentry-docs-24, sentry-docs-55, sentry-docs-56), which together describe uploading source maps via CLI/CI to deobfuscate stack traces. Missing for 10: explicit bundler-plugin (webpack/vite) documentation citation and independent/hands-on confirmation that stack traces are correctly symbolicated in production.

   • [claimed-docs] “Uploading Source Maps”
   • [claimed-docs] “It’s primarily used for managing debug information files for iOS, Android, release and source maps management, as well as code mappings for …”
   • [claimed-docs] “It's primarily used for managing debug information files for iOS, Android, release and source maps management, as well as code mappings for …”
   • [claimed-docs] “Code mappings link stack trace paths to source code paths in your repository. They enable features like source context, suspect commits, sta…”
   • [claimed-docs] “It allows you to create, edit and delete releases as well as upload release artifacts for them.”
   • [probe] “official CLI documented at https://docs.sentry.io/cli/”

   proof ↗⚑ flag

   Honeybadger~partialprobed6/10

   Honeybadger documents a Source Map Upload API for un-minifying JS stack traces (honeybadger-docs-16, honeybadger-docs-28), and it has a general CLI (honeybadger-docs-18, honeybadger-probe-4) with deploy notification support, but the evidence never explicitly shows a CI-oriented source map upload command in that CLI or a bundler plugin (webpack/rollup/vite) for automated CI upload. missing for 10: explicit CLI subcommand or bundler plugin for source map upload, CI usage examples/integration guide, independent confirmation of correct symbolication in production.

   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files. Use the Source Map …”
   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files.”
   • [claimed-docs] “The Honeybadger CLI provides a Command Line Interface for various Honeybadger-related programs and utilities.”
   • [probe] “official CLI documented at https://docs.honeybadger.io/lib/ruby/gem-reference/cli/”

   proof ↗⚑ flag

Symbolication

1. developerUpload dSYM, ProGuard, and native debug symbols so mobile and native crashes symbolicate to real function names and lines

   weight 2 · round to Sentry
   Sentry✓fullprobed8/10

   Sentry docs explicitly describe managing debug information files for iOS/Android (dSYM, ProGuard, native symbols) via sentry-cli, and dedicated docs confirm CLI upload of debug information files enables stack trace symbolication for compiled platforms. Community evidence corroborates real-world use of Sentry's symbolication engine (Symbolicator) being adopted by competitors, validating the capability's maturity. Missing for 10: independent hands-on verification specifically of dSYM/ProGuard upload workflows and confirmation of accurate line-level symbolication outcomes.

   • [claimed-docs] “It’s primarily used for managing debug information files for iOS, Android, release and source maps management, as well as code mappings for …”
   • [claimed-docs] “It's primarily used for managing debug information files for iOS, Android, release and source maps management, as well as code mappings for …”
   • [claimed-docs] “Debug information files allow Sentry to extract stack traces and provide more information about crash reports for most compiled platforms.”
   • [claimed-docs] “It allows you to create, edit and delete releases as well as upload release artifacts for them.”
   • [community] “I know for a fact that your competition is using your code, even where they've built a differentiated service, e.g. Embrace is using Sentry …”
   • [probe] “official CLI documented at https://docs.sentry.io/cli/”

   proof ↗⚑ flag

   Honeybadger—none0/10

   Evidence shows Honeybadger supports JavaScript source map upload/unminification (docs-16, docs-28) but contains no mention of dSYM, ProGuard, or native mobile debug symbol upload/symbolication anywhere in the pack.

   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files. Use the Source Map …”
   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files.”

   proof ↗⚑ flag

Issue trackers

1. developerLink 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

   weight 2 · round to Honeybadger
   Sentry—none0/10

   The evidence pack covers issue status, suspect commits, ownership rules, webhooks, Slack/PagerDuty notifications, and AI/MCP integrations, but contains no mention of Jira, GitHub Issues, or Linear integrations, nor any description of two-way status sync between Sentry issues and external trackers.

   ⚑ flag

   Honeybadger~partialclaimed4/10

   Honeybadger documents issue export/linking to GitHub, GitLab, and Jira (including full Jira wiki markup), and auto-resolves errors on deploy, but there is no evidence of Linear integration nor explicit two-way status sync where resolving/reopening the external ticket automatically resolves/reopens the Honeybadger error (only Slack shows resolve/reopen buttons within Honeybadger itself). missing for 10: Linear integration, documented two-way sync (ticket resolution reopening/closing the Honeybadger error automatically), independent confirmation of sync behavior.

   • [claimed-docs] “We now support detailed issue exports to third-party managers. When enabled, your issue exports to GitHub or GitLab will contain the full ma…”
   • [claimed-docs] “By default, all unresolved errors are automatically marked as resolved when a deployment is recorded, which helps keep your error list clean…”
   • [claimed-docs] “Messages about errors include a button to resolve or reopen the error”

   proof ↗⚑ flag

Scm context

1. developerThe 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

   weight 2 · round to Sentry
   Sentry✓fullclaimed8/10

   Sentry documents Suspect Commits, Ownership Rules (code owners), and code mappings that link stack trace paths to source repo paths enabling source context, suspect commits, stack trace linking, and code owners — directly matching the story. Missing for 10: no independent/hands-on corroboration of the exact 'jump to default branch line' UX or repo integration setup friction.

   • [claimed-docs] “Suspect Commits”
   • [claimed-docs] “Ownership Rules”
   • [claimed-docs] “Code mappings link stack trace paths to source code paths in your repository. They enable features like source context, suspect commits, sta…”
   • [claimed-docs] “Associate Commits”

   proof ↗⚑ flag

   Honeybadger—none0/10

   Evidence shows Honeybadger connects to GitHub/GitLab for deploy diffs and issue exports (docs-7, docs-23), but there is no evidence of suspect-commit identification, code-owner attribution, or jumping from a stack frame to the exact line on the default branch in the repo. Missing for 10: suspect commit detection, code owner mapping, stack-frame-to-source-line deep linking.

   • [claimed-docs] “When GitHub or GitLab is connected, Honeybadger links the revision to a comparison page that shows a diff of what changed since the last dep…”
   • [claimed-docs] “We now support detailed issue exports to third-party managers. When enabled, your issue exports to GitHub or GitLab will contain the full ma…”

   proof ↗⚑ flag