Customer health
Spot the accounts that need attention before they escalate.
AEAcme EuropeCritical42
NSNorthstar LabsWarning68
LCLumen CommerceHealthy86
Platform checking
Customer-aware API observability
Know which customers are affected by API failures.
Apirelio connects errors, releases and API versions to the customers and integrations they impact — without capturing payloads.
Incident impactCustomer healthRelease regressionsVersion adoption
New Ask Apirelio from Claude Code or Codex via MCP → Customer impact tracedAPI failure → affected integration
Inside Apirelio
From an API failure to the customers it affects.
Follow one incident from the first failed request to the affected accounts, with the evidence your team needs to act.
!
Active incident
Detected 17 min agoPayment provider timeouts
Elevated errors on POST /v1/payments
Affected customers3 of 24
Failed requests556
Error rate18.4%
Related release2026.08.12.3
AEAcme Europe438 errors23.8%
NSNorthstar Labs91 errors14.6%
VBVertex Bank27 errors8.8%
01 Errors started 3 min after deploy
02 One endpoint accounts for 96% of failures
03 Only EU production traffic is affected
Illustrative view with simulated data. Open the interactive demo →
Apirelio MCP
Ask your API analytics directly from your coding agent.
Connect Claude Code or OpenAI Codex to project-scoped, read-only analytics. Investigate customer risk, incidents, releases and integration journeys without leaving the terminal.
“Which customers need attention?”“Did this release cause a regression?”“Why is this integration unhealthy?”
8 explicit toolsRead-onlyOne project per tokenNo LLM key required
From telemetry to decisions
See the customer behind every request.
Apirelio turns API traffic into a shared operating view for engineering, support and customer success.
Release impact
Connect a deployment to the precise change in customer experience.
10:04Release deployed
10:07Error rate increased
10:09First customer affected
Integration journey
Track first request, first success, production adoption, time-to-value and stalled implementations.
Make onboarding measurable.Version adoption
Measure traffic share by API version and identify the exact customers that still need migration.
Retire legacy contracts with confidence.What changed?
Get a deterministic comparison of traffic, errors, latency, endpoints and customer movement.
No opaque AI summary required.Alerts and integrations
Detect inactivity, error-rate spikes and traffic drops, then notify Slack, Teams, signed webhooks or email recipients.
Keep the right people informed.Framework-native setup
Production insight in three steps.
Install the SDK
Choose Laravel, Symfony, Nette, Slim, CakePHP, FlightPHP, Express, Fastify, NestJS, Nuxt, FastAPI, Django, Flask, Ruby on Rails, Gin, Fiber, Spring Boot or ASP.NET Core and configure your project ingestion key.
Identify customers
Resolve each authenticated request to its B2B customer and consuming application.
Act on signals
Open the dashboards, investigate regressions and automate alerts and reports.
Works with your stack
Choose a framework-native integration.
PHPLaravelSetup guide →PHPSymfonySetup guide →PHPNetteSetup guide →PHPSlimSetup guide →PHPCakePHPSetup guide →PHPFlightPHPSetup guide →TypeScriptExpressSetup guide →TypeScriptFastifySetup guide →TypeScriptNestJSSetup guide →TypeScriptNuxtSetup guide →PythonFastAPISetup guide →PythonDjango + DRFSetup guide →PythonFlaskSetup guide →RubyRuby on RailsSetup guide →GoGinSetup guide →GoFiberSetup guide →JavaSpring BootSetup guide →.NETASP.NET CoreSetup guide →
Developer documentation
Instrument your first API route.
Choose your PHP, TypeScript, Python, Ruby, Go, Java or .NET framework, follow its quickstart and review the shared privacy-safe event model.
Trust is part of the product
Observe integration health without collecting customer payloads.
Apirelio separates operational analytics from sensitive application data. Project-scoped keys, bounded metadata and configurable retention keep the data surface intentionally small.
Request bodies, response bodies, credentials, cookies and query strings stay out.
Ingestion keys belong to one project, are stored as hashes and can be revoked.
Telemetry delivery runs away from the customer response path and never changes it.
Retention, captured fields and current security posture are documented clearly.
Explore by use case
Customer-aware monitoring for your API stack.
Start with the problem you need to solve or the framework already serving your production traffic.
Use caseCustomer-level API monitoring
Find the exact accounts and integrations affected by errors, latency and releases.
Explore →For teamsAPI monitoring for B2B SaaSGive engineering, support and customer success a shared operating view.
Explore →PHPLaravel API monitoringAdd tenant-aware monitoring through a framework-native package.
Setup guide →PythonFastAPI monitoringConnect endpoint telemetry and exceptions to customer impact.
Setup guide →TypeScriptNestJS API monitoringTrace controller and route issues to the customers behind them.
Setup guide →