What usage data we capture, per provider
An honest, current view of what the AI Explorer can break your AI usage down by — provider by provider. Where a provider reports tokens, you get tokens by model (and project or user where it exists). Where it doesn’t yet, we show the spend and say so — no empty columns implying missing data.
| Provider | Captured today | Tokens | Model | Project | User | Notes |
|---|---|---|---|---|---|---|
| OpenAI | Tokens | Fullest coverage — token usage by model, project, and user via the Usage API. | ||||
| Anthropic (Claude API) | Cost · tokens with admin key | Partial | Partial | Partial | A standard connection tracks cost today; token-level usage (by model and user) needs an Anthropic admin key with Claude Code Analytics enabled. | |
| Claude Code | Cost (today) | Usage arrives via OpenTelemetry as a cost figure today; the per-token metric is received but not yet surfaced as tokens (on the roadmap). | ||||
| Cursor | Tokens | Token-based (Max / API-key) calls carry the full split; request-based calls have no token breakdown. | ||||
| Codex | Credits | Local telemetry in credits by model and user; not broken out into token counts. | ||||
| Google Vertex AI | Tokens | Read from the GCP billing export — no SDK. By model and project; no user axis natively. | ||||
| Gemini API | Tokens | Token-denominated billing SKUs parsed from the GCP export, by model and project. | ||||
| AWS Bedrock | Cost | Spend today via Cost Explorer; model/token-level is on the roadmap (CUR 2.0 / CloudWatch). | ||||
| Azure OpenAI | Cost | Spend today via Cost Management; token-level is on the roadmap (Azure Monitor). | ||||
| Grok (xAI) | Cost | Spend today; token capture (model-level, no user axis) is on the roadmap. | ||||
| Hugging Face | Requests | Partial | Inference requests and cost; no per-token series exists to capture. |
captured today · Partial = limited or needs provider-side setup · not captured today. Cost is always tracked, even where token-level usage isn’t yet.
Why coverage is ragged — and why that’s the honest answer
Every AI provider exposes usage differently. Some hand you tokens by model, project, and user (OpenAI); some give tokens by model with no user axis (Vertex); some only bill per request (Hugging Face) or expose cost with no token feed yet (Bedrock, Azure). StackSpend attributes each provider down to the deepest level it actually supports — and stops there, with a coverage flag explaining why, rather than capping everything at the weakest shared dimension or faking an empty column. Cost is always captured; token depth grows as vendors (and our connectors) expose more.
AI provider coverage — FAQ
Which AI providers report token-level usage in StackSpend?
Does GCP billing show token usage?
Why is some AI spend cost-only?
Can I get per-user AI usage?
Connect your providers and see what flows
Start a free trial, connect your AI and cloud providers, and the AI Explorer shows exactly what usage each one reports — tokens by model where it exists, cost everywhere.