# Unified reporting for all AI Gateway usage

DevFeed: [Unified reporting for all AI Gateway usage](<https://devfeed.tech/articles/unified-reporting-for-all-ai-gateway-usage-779.md>)

Original publisher: [Read original article](<https://vercel.com/blog/unified-reporting-for-your-ai-spend>)

Author: Dan Fein

Published: 2026-03-25T07:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [AI Platform](<https://devfeed.tech/topics/ai-platform.md>), [API](<https://devfeed.tech/topics/api.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [SDKs](<https://devfeed.tech/topics/sdks.md>), [data](<https://devfeed.tech/topics/data.md>), [model-deployment](<https://devfeed.tech/topics/model-deployment.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-gateway](<https://devfeed.tech/tags/ai-gateway.md>), [api](<https://devfeed.tech/tags/api.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [cost](<https://devfeed.tech/tags/cost.md>), [customer](<https://devfeed.tech/tags/customer.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [inference](<https://devfeed.tech/tags/inference.md>), [models](<https://devfeed.tech/tags/models.md>), [platform](<https://devfeed.tech/tags/platform.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [sdk](<https://devfeed.tech/tags/sdk.md>)

## AI overview

Vercel announces the Custom Reporting API for AI Gateway, available in beta for Pro and Enterprise teams. It provides programmatic access to cost, token usage, and request volume across AI Gateway traffic, including BYOK requests, with breakdowns by model, provider, user ID, custom tag, and credential type. The article describes how a platform replaced a third-party proxy and saved over $80K, and explains request tagging and integrations with several AI interfaces.

## Source excerpt

If you're shipping AI features, you already have usage data. 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 $80K One AI platform aggregating models for 200K+ users previously relied on a separate proxy layer to track costs across providers. During the Custom Reporting private beta, they consolidated cost tracking and request management into a single system, replacing their third-party proxy entirely and saving over $80K. With Advanced Reporting, they now use custom tags and user IDs to track customers' usage and costs across models, gaining programmatic access to spend data in the same place their inference already runs. Implement the reporting API Tag requests with user and tags so you can attribute cost in terms your product and finance teams recognize. If you run a customer-facing AI feature, you can tag each request with the customer ID, their plan, and the feature they are using. Tagging works with the AI SDK, Chat Completions API, Responses API, OpenResponses API, and Anthropic Mess