By Nolan Sullivan, Founding Growth EngineerAI cost tracking
The practice of measuring and attributing every dollar an organization spends on AI usage, across personal subscriptions, enterprise licenses, provider API calls, and model routing, so spend is visible in one ledger, mapped to the team that drove it, and controlled before the invoice arrives.
When a board asks what the AI budget returns, most teams cannot answer, because they cannot attribute the spend in the first place. Spend is scattered across personal subscriptions that employees expense, enterprise seats that finance pays for, and provider API keys that engineering manages. Each source reports separately, if it reports at all, so no one owns the total. AI cost tracking is the newest dimension of FinOps, the discipline that brought compute spend under control a decade ago, now extended to the tokens and seats that AI runs on.
Why AI cost tracking is now a finance problem
AI spend has crossed the threshold where finance has to manage it as a category of its own. Gartner forecasts $644 billion in worldwide generative-AI spending in 2025, a 76% jump over the prior year. Spending at that scale and growth rate is exactly what triggered cloud cost discipline, and AI is climbing the same curve faster.
Finance teams have noticed. In the State of FinOps 2026 survey, 98% of FinOps practitioners now manage AI spend, up from 31% two years earlier, and AI cost management ranked as the top skill teams need to build. The discipline that grew up around cloud is being pointed at AI, and the tooling has to follow.
Why AI spend is so hard to track
AI cost tracking is harder than cloud cost tracking for a simple reason: the spend enters from more places, and most of them were never designed to report usage back to a central owner.
- Personal licenses. Employees expense personal Claude, ChatGPT, and Cursor plans on top of company seats. Usage across the two never lands in one place, so the same person’s total cost is split across systems, and those individual licenses raise compliance questions finance and security have to answer.
- No cost attribution. Tokens get billed to a single org-wide key. There is no built-in way to tie spend back to the team, product, or agent that drove it, which makes chargeback impossible.
- Runaway agents. Autonomous agents loop, retry, and burn tokens with no budget, no alert, and no ceiling, so the first signal of a problem is often the invoice.
Each of these is a reporting gap. The provider invoice is accurate; it just describes spend at the wrong level. Tracking AI cost means re-attributing that spend to the people and workloads behind it.
How you track AI costs
Tracking AI cost end to end means putting three capabilities in place: connect every source into one ledger, observe and attribute usage, and control spend before it overruns. The diagram below shows how fragmented spend at the bottom funnels up into a single ledger that feeds each one.
Every call tagged with team, user, agent, and model.
Spend mapped to the cost center that drove it.
Budgets and alerts enforced before the bill lands.
One normalized record of every dollar of AI spend.
Connect every AI source into one ledger
The first stage is collection. Whether spend comes from a personal subscription, an enterprise seat, a provider API key, or a model router, it has to land in one normalized record. That means:
- License tracking across company-issued seats and the personal plans employees expense, side by side in one dashboard.
- API metering at the token level on every call, across Anthropic, OpenAI, and other providers.
- Model router integration that captures cost on every hop, including fallbacks and retries.
- A unified ledger where all of it rolls up into one record of spend, ready to export or analyze.
Without this stage, every later number is partial. Attribution and budgets only mean something once every source reports into the same place.
Observe and attribute usage to teams and agents
The second stage is attribution. Once spend is in one ledger, every request can be logged with the team, user, agent, model, and token count behind it, so finance can slice cost any way it needs:
- Real-time usage that shows spend accruing live, per team, per agent, and per model.
- Cost attribution that tags every call to a team, product, or cost center for confident chargeback or showback.
- Model breakdown that compares cost across models and providers to show what each workload actually costs to run.
- Trend reporting that tracks spend over time and exports for finance reviews and forecasts.
Attribution is also the foundation for ROI. Cost tracking is the first half; once every dollar maps to the workload it funds, you can pair it with the outcomes each team already measures and see which AI investments pay off.
Control spend before the bill arrives
The third stage is enforcement. Visibility after the fact still leaves you reacting to invoices, so budgets have to be set and enforced in real time:
- Budget limits, hard or soft, per team, agent, or key, that block or throttle calls which exceed them.
- Spend alerts that fire when usage crosses a threshold, so a surprise hits a Slack channel instead of an invoice.
- Runaway protection that detects loops and abnormal token bursts and caps the agent before it drains the budget.
- Rate and quota controls that keep spend predictable across the organization.
The AI cost tracking maturity model
Companies reach AI cost tracking in stages, as spend outgrows the approach before it. Most can place themselves on a four-stage curve, and knowing the stage tells you what to build next.
Employees expense personal AI plans on corporate cards. No central owner, no view of the total.
Enterprise licenses cover most usage, but personal plans linger and only the enterprise spend is visible.
Spend from enterprise and personal licenses lands in one ledger, so the whole AI footprint is visible.
Every dollar maps to the team and outcome it funds, so spend can be measured against what it returns.
Stage one: unmanaged
AI spend lives on corporate cards. Employees expense personal Claude, ChatGPT, and Cursor plans, and no one owns the total. Finance sees a scatter of line items on expense reports with no way to roll them up. The tooling is whatever finance already runs: corporate card statements, expense tools like Brex or Expensify, and a spreadsheet to pull them together.
Stage two: enterprise licenses
The company buys enterprise licenses that cover most AI usage, so the bulk of spend now runs through a contract finance can see. Personal plans still linger at the edges, and only the enterprise usage shows up, so the picture looks more complete than it is. Visibility comes from provider billing consoles and SaaS management or procurement tools that track license seats, none of which see usage below the contract.
Stage three: full visibility
Spend from both enterprise and personal licenses lands in one ledger. The whole AI footprint is visible, including the personal plans that used to hide on expense reports, so finance can state the real total. This stage needs tooling built for it: a unified ledger that pulls provider APIs and license data into one record, whether a FinOps platform extended to AI or a dedicated AI cost tool.
Stage four: attributed to outcomes
Cost maps to the team, product, and business outcome it funds. With every dollar attributed, AI spend can be measured against what it returns, so finance can answer which investments pay off instead of only what they cost. Attribution at this level depends on something in the path of every call, an AI gateway or control plane that tags each request and feeds the BI and finance systems where outcomes are already measured.
Most companies sit at stage two, where enterprise licensing creates a sense of coverage while personal usage stays invisible. Moving up the curve depends on the same foundation at every step, every source reporting into one ledger.
How Speakeasy tracks AI cost
Cost tracking only works if something sits in the path of every AI call. Speakeasy is building the AI control plane, and because it sits on that path, metering, attribution, and budget enforcement happen on every request rather than being reconstructed from invoices later.
- One unified ledger. Spend from Anthropic, OpenAI, and licensed tools is normalized into a single source of truth, so the full AI footprint sits in one place.
- Chargeback and showback. Every call is attributed to a team, product, or cost center, so cost maps back to who drove it for internal billing and accountability.
- Personal and enterprise usage together. Usage from personal and company licenses is attributed to the same person, so the blind spot of expensed personal plans finally closes.
- Budgets enforced in real time. Limits per team, agent, or key are enforced on the path, blocking, throttling, or alerting before spend crosses a threshold.
- Export anywhere. Usage and cost records export in standard formats for BI tools, data warehouses, and finance systems.
Because the same control plane already governs which tools an agent can call and produces the audit trail behind every action, cost tracking comes with the controls platform and security teams rely on. For teams starting an AI cost program, the unified ledger is the right first step: attribution and budgets both depend on every source reporting into one place.