What is AI cost tracking?

Posted on Oct 29 • Originally published at speakeasy.com

By Nolan Sullivan, Founding Growth Engineer at Speakeasy. Originally published on Speakeasy.

One org-wide API key hides who drove the bill. Why AI spend is hard to attribute, how to track it in three stages, and a maturity model for finance and platform teams.

AI cost tracking is 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. Spend becomes 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, answering is hard because the spend is all over the place. It 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.

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 managing AI spend now ranks as their top forward-looking priority. The discipline that grew up around cloud is being pointed at AI, and the tooling has to follow.

AI cost tracking is harder than cloud cost tracking because AI spend enters from more places, and most of them were never designed to report usage back to a central owner.

Each of these is a reporting gap. The provider invoice is accurate, but it describes spend at the wrong level. Tracking AI cost means re-attributing that spend to the people and workloads behind it.

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 linked below shows how fragmented spend at the top funnels down into a single ledger that feeds each one.

View the AI cost tracking flow diagram on Speakeasy.

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:

Without this stage, every later number is partial. Attribution and budgets only mean something once every source reports into the same place.

The second stage is AI cost 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:

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.

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:

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.

View the AI cost tracking maturity model diagram on Speakeasy.

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.

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.

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.

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.

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.

Because the same control plane already governs which tools an agent can call and produces the audit trail behind every action, AI 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, because attribution and budgets both depend on every source reporting into one place.

AI cost tracking is the practice of measuring and attributing every dollar an organization spends on AI, across enterprise licenses, provider API calls, and model routing. It normalizes spend from every source into one ledger, ties each cost back to the team, user, or agent that drove it, and enforces budgets before the invoice arrives. It is the AI equivalent of cloud cost management, or FinOps, applied to tokens and seats instead of compute.

The discipline is the same, but the unit of spend is different. Cloud cost management attributes compute, storage, and network to teams and services. AI cost tracking attributes tokens, model calls, and seat licenses. The harder part is that AI spend is more fragmented: it arrives through provider APIs, enterprise seats, and personal subscriptions employees expense, and a single org-wide API key often hides which team actually drove the usage.

Every call routed through Speakeasy is metered at the token level and normalized into a single ledger, so spend from Anthropic, OpenAI, and other providers shows up in one view. Licensed-tool usage reports into the same place, giving finance one source of truth instead of a stack of invoices.

Yes. Every request is tagged with team, user, agent, and model, so cost maps back to who drove it. Use the tags for chargeback to a cost center or showback to a team, the same way cloud cost is allocated today.

Both. Speakeasy brings licensed-tool usage, such as ChatGPT Enterprise and Copilot seats, and provider API spend into the same dashboard, so the full AI footprint sits in one ledger rather than split across finance and engineering systems.

Yes. Most teams have employees running personal Claude, ChatGPT, and Cursor plans alongside company seats, and tracking spend across both is a real blind spot. Speakeasy attributes usage from personal and enterprise licenses to the same person, so total cost per employee is finally visible in one place.

Set hard or soft caps per team, agent, or key. Speakeasy enforces them in real time and can block, throttle, or alert when spend crosses a threshold, so a runaway workload hits a Slack channel instead of an invoice.

Speakeasy detects abnormal token bursts and loops, then caps the agent before it drains the budget. Alerts fire in real time so the team can step in rather than discovering the spend at the end of the billing cycle.

Cost tracking is the first half of ROI. Speakeasy attributes every dollar to the team, agent, and workload behind it, so spend connects to the work it funds. Pair that with the outcomes each team already tracks to see which AI investments pay off and which to cut.

Yes. Usage and cost records export in standard formats for finance reviews, BI tools, data warehouses, and forecasting, so AI spend lands in the same systems that already track the rest of the budget.