Try itExperimental
See what an agent can do with Honeybadger before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); the live MCP handshake runs real requests from our edge, right now — including, where the server allows it, one real read-only tool call (bring your own key for auth-gated servers); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -s https://app.honeybadger.io/v2/projects # the documented Data API, keyless → access deniedrecorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Ai debugging — stories about ai debugging in this arenaAi debuggingevidence →
Stories about ai debugging in this arena
Alerting noise — stories about alerting noise in this arenaAlerting noiseevidence →
Stories about alerting noise in this arena
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Data scrubbing — stories about data scrubbing in this arenaData scrubbingevidence →
Stories about data scrubbing in this arena
Error data access — stories about error data access in this arenaError data accessevidence →
Stories about error data access in this arena
Grouping triage — stories about grouping triage in this arenaGrouping triageevidence →
Stories about grouping triage in this arena
Impact analytics — stories about impact analytics in this arenaImpact analyticsevidence →
Stories about impact analytics in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Quotas cost — stories about quotas cost in this arenaQuotas costevidence →
Stories about quotas cost in this arena
Releases regressions — stories about releases regressions in this arenaReleases regressionsevidence →
Stories about releases regressions in this arena
Sdk instrumentation — stories about sdk instrumentation in this arenaSdk instrumentationevidence →
Stories about sdk instrumentation in this arena
Search analytics — stories about search analytics in this arenaSearch analyticsevidence →
Stories about search analytics in this arena
Sourcemaps symbolication — stories about sourcemaps symbolication in this arenaSourcemaps symbolicationevidence →
Stories about sourcemaps symbolication in this arena
Workflow integrations — stories about workflow integrations in this arenaWorkflow integrationsevidence →
Stories about workflow integrations in this arena
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 0 free · 0 paid · 1 enterprise · 33 not stated in evidence
Follow the green: where the map greys out is where Honeybadger stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Machine-readable spec · Versioning policy · Capture native mobile crashes — iOS, Android, NDK — with the device, OS, and app-version context needed to reproduce them · The platform connects to my repos so an issue shows suspect commits and code owners, and I can jump from a stack frame to the exact line on my default branch
Subscribe to events via webhooks
~3/10
Build against official SDKs
~6/10
Issue scoped/least-privilege API credentials for an agent
~3/10
Connect an agent via an official MCP server
✓9/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
n/an/a
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓8/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
~3/10
Operate the product with natural-language commands
~6/10
Plug MCP servers into this product so it can use their tools
n/an/a
Get AI-generated insights and suggestions from my data inside the product
~6/10
Set up automations that run autonomously in the background
~5/10
Ai debugging — stories about ai debugging in this arenaAi debugging
Stories about ai debugging in this arena
Alerting noise — stories about alerting noise in this arenaAlerting noise
Stories about alerting noise in this arena
Route alerts by project, environment, and severity to Slack, PagerDuty, or email with per-rule thresholds — new issue, frequency spike, affected-user count
~6/10
Fight alert fatigue with spike protection, per-key rate limits, and mute/ignore rules so one bad deploy doesn't page the whole team all night
~4/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Data scrubbing — stories about data scrubbing in this arenaData scrubbing
Stories about data scrubbing in this arena
Error data access — stories about error data access in this arenaError data access
Stories about error data access in this arena
An agent can pull my top production issues with stack traces via API or MCP, triage them, and file the real bugs into my tracker
~6/10
List, query, and update issues and fetch raw events through a documented REST API with scoped tokens
~5/10
The event-ingestion protocol is documented and open enough that custom clients and compatible SDKs can send events without an official SDK
✓7/10
Grouping triage — stories about grouping triage in this arenaGrouping triage
Stories about grouping triage in this arena
Impact analytics — stories about impact analytics in this arenaImpact analytics
Stories about impact analytics in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Quotas cost — stories about quotas cost in this arenaQuotas cost
Stories about quotas cost in this arena
Releases regressions — stories about releases regressions in this arenaReleases regressions
Stories about releases regressions in this arena
I get alerted when an error that was fixed comes back in a newer release, distinct from ordinary new-issue noise
~5/10
Watch release health — crash-free sessions and users, adoption per release — and compare a canary release against the last stable one
—0/10
Associate errors with releases and commits so each issue shows the release it first appeared in and the suspect commit that likely caused it
~5/10
Sdk instrumentation — stories about sdk instrumentation in this arenaSdk instrumentation
Stories about sdk instrumentation in this arena
Attach breadcrumbs, custom tags, and user context to every event so a stack trace arrives with the state that produced it
~4/10
Capture native mobile crashes — iOS, Android, NDK — with the device, OS, and app-version context needed to reproduce them
—0/10
Instrument my web frontend, backend services, and mobile apps with official SDKs that capture uncaught errors automatically
~6/10
Search analytics — stories about search analytics in this arenaSearch analytics
Stories about search analytics in this arena
Sourcemaps symbolication — stories about sourcemaps symbolication in this arenaSourcemaps symbolication
Stories about sourcemaps symbolication in this arena
Workflow integrations — stories about workflow integrations in this arenaWorkflow integrations
Stories about workflow integrations in this arena
Link an error to Jira, GitHub Issues, or Linear with two-way status sync, so fixing the ticket resolves the error and a regression reopens it
~4/10
The platform connects to my repos so an issue shows suspect commits and code owners, and I can jump from a stack frame to the exact line on my default branch
—0/10
Sorted by importance (agentic first) (high → low) · 55/55 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 9/10 | Tprobed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 3/10 | Cclaimed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | 0/10 | ||
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 6/10 | Tprobed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 6/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 3/10 | Tprobed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 3/10 | Cclaimed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | n/a | untested | none yet | |
The platform groups thousands of duplicate events into one issue via stack-trace fingerprinting, and I can customize the grouping when it gets it wrong C Grouping | developer | Grouping triage — stories about grouping triage in this arenaGrouping triage | 3 | full | 8/10 | Xcommunity | |
An agent can pull my top production issues with stack traces via API or MCP, triage them, and file the real bugs into my tracker C Agent access | ai-native user | Error data access — stories about error data access in this arenaError data access | 3 | partial | 6/10 | Tprobed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 6/10 | Cclaimed | |
Instrument my web frontend, backend services, and mobile apps with official SDKs that capture uncaught errors automatically C Sdk coverage | developer | Sdk instrumentation — stories about sdk instrumentation in this arenaSdk instrumentation | 3 | partial | 6/10 | Cclaimed | |
Route alerts by project, environment, and severity to Slack, PagerDuty, or email with per-rule thresholds — new issue, frequency spike, affected-user count C Alert routing | sre | Alerting noise — stories about alerting noise in this arenaAlerting noise | 3 | partial | 6/10 | Cclaimed | |
Upload JavaScript source maps from CI — via CLI or bundler plugin — so production stack traces show my original source, not minified frames C Sourcemaps | developer | Sourcemaps symbolication — stories about sourcemaps symbolication in this arenaSourcemaps symbolication | 3 | partial | 6/10 | Tprobed | |
Associate errors with releases and commits so each issue shows the release it first appeared in and the suspect commit that likely caused it C Release tracking | developer | Releases regressions — stories about releases regressions in this arenaReleases regressions | 3 | partial | 5/10 | Cclaimed | |
List, query, and update issues and fetch raw events through a documented REST API with scoped tokens C Api access | developer | Error data access — stories about error data access in this arenaError data access | 3 | partial | 5/10 | Cclaimed | |
Triage issues — assign an owner, resolve, ignore, or snooze — and the platform reopens a resolved issue automatically when it regresses C Triage | sre | Grouping triage — stories about grouping triage in this arenaGrouping triage | 3 | partial | 5/10 | Cclaimed | |
The platform's AI analyzes an issue — stack trace, breadcrumbs, related commits — and proposes a root cause I can act on C Root cause | ai-native user | Ai debugging — stories about ai debugging in this arenaAi debugging | 3 | partial | 4/10 | Tprobed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partialenterprise | 3/10 | Cclaimed | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Search and filter events across projects by tag, release, environment, and custom properties with a real query syntax C Event search | developer | Search analytics — stories about search analytics in this arenaSearch analytics | 2 | full | 8/10 | Cclaimed | |
The event-ingestion protocol is documented and open enough that custom clients and compatible SDKs can send events without an official SDK C Ingest protocol | developer | Error data access — stories about error data access in this arenaError data access | 2 | full | 7/10 | Tprobed | |
See error trends across projects and teams on dashboards — top regressions, new issues per release, volume over time C Dashboards | engineering leader | Search analytics — stories about search analytics in this arenaSearch analytics | 2 | partial | 6/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 5/10 | Tprobed | |
I get alerted when an error that was fixed comes back in a newer release, distinct from ordinary new-issue noise C Regressions | sre | Releases regressions — stories about releases regressions in this arenaReleases regressions | 2 | partial | 5/10 | Cclaimed | |
Attach breadcrumbs, custom tags, and user context to every event so a stack trace arrives with the state that produced it C Event context | developer | Sdk instrumentation — stories about sdk instrumentation in this arenaSdk instrumentation | 2 | partial | 4/10 | Cclaimed | |
Fight alert fatigue with spike protection, per-key rate limits, and mute/ignore rules so one bad deploy doesn't page the whole team all night C Noise control | sre | Alerting noise — stories about alerting noise in this arenaAlerting noise | 2 | partial | 4/10 | Cclaimed | |
Link an error to Jira, GitHub Issues, or Linear with two-way status sync, so fixing the ticket resolves the error and a regression reopens it C Issue trackers | developer | Workflow integrations — stories about workflow integrations in this arenaWorkflow integrations | 2 | partial | 4/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 4/10 | Cclaimed | |
Capture native mobile crashes — iOS, Android, NDK — with the device, OS, and app-version context needed to reproduce them C Mobile crashes | developer | Sdk instrumentation — stories about sdk instrumentation in this arenaSdk instrumentation | 2 | none | 0/10 | ||
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | n/a | 0/10 | ||
The platform connects to my repos so an issue shows suspect commits and code owners, and I can jump from a stack frame to the exact line on my default branch C Scm context | developer | Workflow integrations — stories about workflow integrations in this arenaWorkflow integrations | 2 | none | 0/10 | ||
The platform's AI can draft a code fix for an error and open a pull request against my repo for human review C Autofix | ai-native user | Ai debugging — stories about ai debugging in this arenaAi debugging | 2 | none | 0/10 | ||
Upload dSYM, ProGuard, and native debug symbols so mobile and native crashes symbolicate to real function names and lines C Symbolication | developer | Sourcemaps symbolication — stories about sourcemaps symbolication in this arenaSourcemaps symbolication | 2 | none | 0/10 | ||
Watch release health — crash-free sessions and users, adoption per release — and compare a canary release against the last stable one C Release health | sre | Releases regressions — stories about releases regressions in this arenaReleases regressions | 2 | none | 0/10 | ||
Cap event quotas per project and set spend limits so an error storm burns a predictable budget, never a surprise invoice G Quotas | engineering leader | Quotas cost — stories about quotas cost in this arenaQuotas cost | 2 | none | untested | none yet | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Every issue quantifies real impact — how many users and sessions are affected — so I prioritize by blast radius, not raw event counts C User impact | sre | Impact analytics — stories about impact analytics in this arenaImpact analytics | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | untested | none yet | |
Scrub PII from error events — server-side scrubbing rules plus SDK-level filtering — before sensitive payloads ever persist C Pii scrubbing | sre | Data scrubbing — stories about data scrubbing in this arenaData scrubbing | 2 | none | untested | none yet | |
Merge issues that are really the same bug and split ones the fingerprinter wrongly collapsed C Triage | developer | Grouping triage — stories about grouping triage in this arenaGrouping triage | 1 | partial | 5/10 | Cclaimed | |
Collect user feedback — a crash-report dialog or feedback widget — attached to the exact error event the user hit C User feedback | developer | Impact analytics — stories about impact analytics in this arenaImpact analytics | 1 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | n/a | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 43 stories with headroom
What would move Honeybadger’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product
partialq3/10moves Built-in AIimpact 31.5
Missing: 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.
Openness — open source, data portability, and self-hosting storiesSelf-host the core product
nonemoves PA Scoreimpact 30
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.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
Missing: any privacy policy statement on AI training data usage, opt-out mechanism, or data processing terms addressing AI model training.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
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.
Agenticness — how well agents can access and operate the productDownload a machine-readable API spec (OpenAPI or equivalent)
nonemoves API qualityimpact 30
Missing: an actual OpenAPI/Swagger JSON or YAML file, any documented spec download link, or generator tooling.
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
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.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
partialq3/10moves PA Scoreimpact 21
Missing: dedicated full-account data export feature, documented open-format bulk export tool, evidence of complete data portability/leave workflow.
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
partialq3/10moves agent-readyimpact 21
Missing: explicit scoped/least-privilege API key creation, granular permission levels for agent credentials, documentation of restricting MCP/agent access to specific resources.
Showing the top 8 of 43 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map10 surfaces · 33 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Guides docs22 stories
- Run the product headlessly / in CI for automation
- Build against official SDKs
- Subscribe to events via webhooks
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Route alerts by project, environment, and severity to Slack, PagerDuty, or email with per-rule thresholds — new issue, frequency spike, affected-user count
- Fight alert fatigue with spike protection, per-key rate limits, and mute/ignore rules so one bad deploy doesn't page the whole team all night
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- List, query, and update issues and fetch raw events through a documented REST API with scoped tokens
- The platform groups thousands of duplicate events into one issue via stack-trace fingerprinting, and I can customize the grouping when it gets it wrong
- Triage issues — assign an owner, resolve, ignore, or snooze — and the platform reopens a resolved issue automatically when it regresses
- Merge issues that are really the same bug and split ones the fingerprinter wrongly collapsed
- I get alerted when an error that was fixed comes back in a newer release, distinct from ordinary new-issue noise
- Associate errors with releases and commits so each issue shows the release it first appeared in and the suspect commit that likely caused it
- Attach breadcrumbs, custom tags, and user context to every event so a stack trace arrives with the state that produced it
- Instrument my web frontend, backend services, and mobile apps with official SDKs that capture uncaught errors automatically
- See error trends across projects and teams on dashboards — top regressions, new issues per release, volume over time
- Search and filter events across projects by tag, release, environment, and custom properties with a real query syntax
- Link an error to Jira, GitHub Issues, or Linear with two-way status sync, so fixing the ticket resolves the error and a regression reopens it
Resources docs11 stories
- Point an agent at llms.txt or agent-oriented docs
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Issue scoped/least-privilege API credentials for an agent
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- The platform's AI analyzes an issue — stack trace, breadcrumbs, related commits — and proposes a root cause I can act on
- An agent can pull my top production issues with stack traces via API or MCP, triage them, and file the real bugs into my tracker
- Do everything through the API that I can do in the UI
API reference11 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- An agent can pull my top production issues with stack traces via API or MCP, triage them, and file the real bugs into my tracker
- List, query, and update issues and fetch raw events through a documented REST API with scoped tokens
- The event-ingestion protocol is documented and open enough that custom clients and compatible SDKs can send events without an official SDK
- Triage issues — assign an owner, resolve, ignore, or snooze — and the platform reopens a resolved issue automatically when it regresses
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Instrument my web frontend, backend services, and mobile apps with official SDKs that capture uncaught errors automatically
- Upload JavaScript source maps from CI — via CLI or bundler plugin — so production stack traces show my original source, not minified frames
Changelog docs9 stories
- Connect an agent via an official MCP server
- Issue scoped/least-privilege API credentials for an agent
- Build against official SDKs
- An agent can pull my top production issues with stack traces via API or MCP, triage them, and file the real bugs into my tracker
- Export all of my data in open formats and leave
- Attach breadcrumbs, custom tags, and user context to every event so a stack trace arrives with the state that produced it
- Instrument my web frontend, backend services, and mobile apps with official SDKs that capture uncaught errors automatically
- Search and filter events across projects by tag, release, environment, and custom properties with a real query syntax
- Link an error to Jira, GitHub Issues, or Linear with two-way status sync, so fixing the ticket resolves the error and a regression reopens it
_llms txt docs8 stories
- Point an agent at llms.txt or agent-oriented docs
- Build against official SDKs
- Perform bulk operations across many items at once
- The event-ingestion protocol is documented and open enough that custom clients and compatible SDKs can send events without an official SDK
- Do everything through the API that I can do in the UI
- Instrument my web frontend, backend services, and mobile apps with official SDKs that capture uncaught errors automatically
- See error trends across projects and teams on dashboards — top regressions, new issues per release, volume over time
- Search and filter events across projects by tag, release, environment, and custom properties with a real query syntax
Lib docs6 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Build against official SDKs
- Do everything through the API that I can do in the UI
- Upload JavaScript source maps from CI — via CLI or bundler plugin — so production stack traces show my original source, not minified frames
OpenAPI spec4 stories
Hacker News1 story
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -s https://app.honeybadger.io/v2/projects # the documented Data API, keyless → access deniedreproduced$ curl -s https://app.honeybadger.io/v2/projects # the documented Data API, [redacted]less → access denied
{"errors":"Access denied"}
$curl -si -X POST https://mcp.honeybadger.io/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # Honeybadger's hosted MCP server, keyless → OAuth challengereproduced$ curl -si -X POST https://mcp.honeybadger.io/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # Honeybadger's hosted MCP server, [redacted]less → OAuth challenge HTTP/2 401 www-authenticate: Bearer resource_metadata="https://mcp.honeybadger.io/.well-known/oauth-protected-resource/mcp"
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
8 of 17 testable claims verified · 1 contradicted → integrity 35/100
25 distinct capability claims found in Honeybadger’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
8
Verified
8
Unverified
1
Contradicted
17
Undersold
Verified (11)
“Lets you customize error grouping via error class, component, stack trace, or custom fingerprint”
The platform groups thousands of duplicate events into one issue via stack-trace fingerprinting, and I can customize the grouping when it gets it wrongfullproof ↗
“Groups identical errors into one issue while letting you browse each individual occurrence”
The platform groups thousands of duplicate events into one issue via stack-trace fingerprinting, and I can customize the grouping when it gets it wrongfullproof ↗
“Lets you describe a search in plain language and have it generate the query for you”
Operate the product with natural-language commandspartialproof ↗
“Anomaly detection alerts you when error volume deviates statistically from a learned baseline”
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
“Official CLI command to show details of a specific fault by number”
“Connecting via MCP gives an AI assistant project management, error investigation, and BadgerQL insight capabilities”
“Hosted MCP server supports OAuth so agents can connect via browser approval instead of pasting credentials”
“Errors can be submitted as a JSON payload via a documented POST endpoint”
The event-ingestion protocol is documented and open enough that custom clients and compatible SDKs can send events without an official SDKfullproof ↗
“Un-minifies JavaScript stack traces automatically when source maps are uploaded”
Upload JavaScript source maps from CI — via CLI or bundler plugin — so production stack traces show my original source, not minified framespartialproof ↗
“Ships an official command-line interface for Honeybadger-related tasks”
“Requests from Honeybadger servers include a secret Honeybadger-Token header derived from the API key”
Issue scoped/least-privilege API credentials for an agentpartialproof ↗
Unverified (12)
“Automatically captures and sends errors thrown by an instrumented application to Honeybadger's API”
Instrument my web frontend, backend services, and mobile apps with official SDKs that capture uncaught errors automaticallypartialproof ↗
“Supports a structured query syntax to filter errors by class, tag, component, and action”
Search and filter events across projects by tag, release, environment, and custom properties with a real query syntaxfullproof ↗
“Automatically marks unresolved errors as resolved when a new deployment is recorded”
Triage issues — assign an owner, resolve, ignore, or snooze — and the platform reopens a resolved issue automatically when it regressespartialproof ↗
“Links a deploy revision to a diff view showing code changes since the last deploy when GitHub/GitLab is connected”
Associate errors with releases and commits so each issue shows the release it first appeared in and the suspect commit that likely caused itpartialproof ↗
“Lets you define alarms combining a BadgerQL query with a threshold to trigger alerts”
Define rules that trigger actions automatically on eventspartialproof ↗
“Notification messages include a button to resolve or reopen the error directly”
Triage issues — assign an owner, resolve, ignore, or snooze — and the platform reopens a resolved issue automatically when it regressespartialproof ↗
“Integrates with PagerDuty by generating a service integration key for alert routing”
Route alerts by project, environment, and severity to Slack, PagerDuty, or email with per-rule thresholds — new issue, frequency spike, affected-user countpartialproof ↗
“Provides an API endpoint to notify Honeybadger when a deploy occurs”
Associate errors with releases and commits so each issue shows the release it first appeared in and the suspect commit that likely caused itpartialproof ↗
“API endpoint returns a list of faults or a single fault for a given project”
List, query, and update issues and fetch raw events through a documented REST API with scoped tokenspartialproof ↗
“Supports querying errors that occurred since the most recent deployment”
Search and filter events across projects by tag, release, environment, and custom properties with a real query syntaxfullproof ↗
“Detailed issue exports to GitHub, GitLab, or Jira include full markdown/wiki content”
Link an error to Jira, GitHub Issues, or Linear with two-way status sync, so fixing the ticket resolves the error and a regression reopens itpartialproof ↗
“Integrates with Oban to report unhandled worker exceptions and per-job telemetry to Insights”
Instrument my web frontend, backend services, and mobile apps with official SDKs that capture uncaught errors automaticallypartialproof ↗
Contradicted (1)
“Business/Enterprise accounts can replicate Insights data to retain it longer than default storage”
Undersold (17)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationfullproof ↗
Drive the product through a documented public APIfullproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Delegate tasks to a built-in AI assistant inside the productpartialproof ↗
The platform's AI analyzes an issue — stack trace, breadcrumbs, related commits — and proposes a root cause I can act onpartialproof ↗
Fight alert fatigue with spike protection, per-key rate limits, and mute/ignore rules so one bad deploy doesn't page the whole team all nightpartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
An agent can pull my top production issues with stack traces via API or MCP, triage them, and file the real bugs into my trackerpartialproof ↗
Merge issues that are really the same bug and split ones the fingerprinter wrongly collapsedpartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Export all of my data in open formats and leavepartialproof ↗
I get alerted when an error that was fixed comes back in a newer release, distinct from ordinary new-issue noisepartialproof ↗
Attach breadcrumbs, custom tags, and user context to every event so a stack trace arrives with the state that produced itpartialproof ↗
See error trends across projects and teams on dashboards — top regressions, new issues per release, volume over timepartialproof ↗
Claims outside our story set (1)
Real capability claims found in Honeybadger’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Supports SAML assertion attributes to map existing roles/teams into a Honeybadger project”
source ↗
Business model
Developer plan is free forever; Team is $26/mo and Business $80/mo; the top tier adds enterprise security and compliance.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
