Key Takeaways
- The problem is that it's split across providers, keys, and dashboards, so it's hard to answer basic questions before the bill shows up.
- You've probably felt the drift into after-the-fact reconciliation.
- Provider consoles only show their own slice, so you end up exporting CSVs, rebuilding views in spreadsheets, and still missing the context that matters, like your tags, feature boundaries, and…
Why It Matters
Context
The problem is that it's split across providers, keys, and dashboards, so it's hard to answer basic questions before the bill shows up. You've probably felt the drift into after-the-fact reconciliation. Provider consoles only show their own slice, so you end up exporting CSVs, rebuilding views in spreadsheets, and still missing the context that matters, like your tags, feature boundaries, and internal user IDs. When BYOK enters the picture, it gets worse because spend and usage scatter across whatever keys your users bring. The Custom Reporting API for AI Gateway is now available in beta for teams on the Pro and Enterprise plans. It gives you programmatic access to cost, token usage, and request volume across your AI Gateway traffic, including BYOK requests. You can break down spend by model, provider, user ID, custom tag, or credential type. That makes it possible to track costs and usage per feature, per end customer, and per pricing tier from a single endpoint. You can also query it live via Claude Code. How a platform saved $80 KOne AI platform aggregating models for 200 K+ users previously relied on a separate proxy layer to track costs across providers. During the Custom…
For Builders
The problem is that it's split across providers, keys, and dashboards, so it's hard to answer basic questions before the bill shows up.