OpenAI tokens, attributed like any other cost.

CloudMonitor reads your OpenAI usage into Fabric and turns a single API invoice into cost per team, per project, and per model, with anomalies caught the day they start.

Try the beta

See pricing

OpenAI bills per token, and that bill grows fast once GPT calls hit production. CloudMonitor breaks the invoice apart by model, by token type, and by the project or team that drove it, so spend has an owner and a unit cost rather than one opaque number on a monthly statement.

Breaks GPT spend down by model and by input, output, and cached tokens.
Attributes usage to teams, projects, users, and API keys, not just one org total.
Catches token-spend spikes from prompt or routing changes within the day.
Builds a showback ledger so AI cost lands on the budget that owns it.

Provider breakdown

See where the OpenAI bill actually goes.

CloudMonitor splits OpenAI spend by model, project, user, and API key, across Chat, Embeddings, Images, Audio, Vector Stores, and Code Interpreter, so you can steer routine calls toward cheaper models with the evidence to back it.

Model mix across the GPT and o-series family, with reasoning tokens surfaced as a Thinking tokens KPI
Input, output, and cached token split per workload
Per-project and per-API-key attribution

Anomaly detection

A routing change should not wait for the invoice.

Because token cost is incurred the moment a request runs, CloudMonitor forecasts daily OpenAI spend and fires an alert when usage jumps, routed to the team behind it with the dollar impact attached.

Daily token-spend forecast per team and project
Spike alerts for prompt and routing changes
Routed to Teams with owner and impact attached

Showback

Put AI cost on the budget that owns it.

A per-team ledger reconciles OpenAI spend against the project and cost center it belongs to, so finance can charge it back and product can see cost per unit of value next to the volume it shipped.

Per-team and per-project cost ledger
Cost per unit of value alongside volume
Chargeback-ready for finance

Token economics

Why OpenAI spend needs more than a SaaS line item.

AI cost is set the moment a request runs. A longer prompt, an extra retry, or a switch to a larger model can move spend in seconds, not billing cycles. CloudMonitor treats every token as a unit of cost you can attribute, forecast, and tie back to the work it produced.

The cost unit changed

Cloud spend is a vCPU-hour or a GB-month. OpenAI spend is a token, an inference call, and an agent session, measured per request and billed as it happens.

Allocate before you spend

Infrastructure FinOps reports after the bill lands. AI spend has to be attributed at the point of the call, so a runaway loop is caught in minutes, not on next month's invoice.

Unit economics, not totals

A single invoice number tells finance nothing. CloudMonitor reduces OpenAI usage to cost per team, per feature, and per unit of value: the conversation, the task, the pull request.

AI cost management is now near-universal: 98% of practitioners report governing AI spend, up from 31% two years earlier, and it ranks as the top skill FinOps teams are building. Source: State of FinOps 2026 Report

Billing model

API-direct token billing (you pay OpenAI per token), plus ChatGPT subscription seats.

What drives the bill

Model tier: reasoning models in the o-series cost far more per token than mini models.
Token type: output tokens are priced above input tokens, though cached input is heavily discounted.
Batch vs standard: asynchronous batch requests run at roughly half the standard rate.
Shadow keys: ungoverned API keys create spend nobody is tracking.

What CloudMonitor does show

Cost per team, project, and environment, not just one org total.
Model mix and input-versus-output split for every workload.
Daily forecast with spike alerts before the invoice arrives.
A chargeback-ready ledger tying spend to the work it produced.

CloudMonitor's approach aligns with the FinOps Foundation's Token Economics & SaaS working group, the emerging discipline for governing pay-per-token cost.

An OpenAI API key is easy to share and hard to govern. Usage spreads across projects, the invoice climbs, and finance is left with a single number nobody can explain. CloudMonitor reads OpenAI usage into your Fabric workspace with an org-level Admin API key and rebuilds that number into cost per team, per project, and per model.

The same engine that allocates and forecasts your Azure and Anthropic spend applies to OpenAI tokens, so GPT cost is governed with the same discipline as the rest of the estate rather than living in a spreadsheet on the side.

Read about FinOps for AI →

More ai & llm