Skip to content

Cost and FinOpsGuide

Where AI spend fits in the FinOps Framework: a capability map

If you already run cloud FinOps, AI spend on provider keys you hold fits the Framework you know. This guide maps allocation, anomaly management, forecasting and unit economics to the data sources and gateway fields that feed them, and says where the numbers are estimates.

By INFRO Editorial

Published

10 min read

Glowing token streams being compressed into a precise efficient AI infrastructure pipeline

In short

AI spend is a Technology Category inside the FinOps Framework, so the capabilities you already run apply to it; what changes is the data. On customer-held provider keys, allocation, anomaly, forecasting and unit economics need request-level metadata from your gateway, reconciled to the provider's own cost figures.2

Key takeaways

  • AI is a Technology Category in the FinOps Framework, and most capabilities carry over; the gap is allocation data, because direct provider bills rarely carry tags.
  • Put the dimensions finance reports on (workflow, feature, customer, team) on every request at the gateway, because nothing is backfilled afterwards.
  • Treat gateway cost as an estimate that sits in FOCUS ListCost and ContractedCost, and populate BilledCost only from the provider's own reported figure.
  • Forecast AI with drivers (units of work times calls per unit times tokens per call), report the result as a range, and let anomaly and drift alerts tell you when the drivers moved.
  • Report unit cost with its unpriced share beside it, so a partial figure never reads as a whole one.

Where AI spend sits in the Framework

The FinOps Framework is built from principles, personas, phases, domains, capabilities and scopes, and it describes itself as flexible and non-prescriptive: you start where the need is greatest and grow in scale and maturity.1 AI appears there as a Technology Category beside Public Cloud, SaaS, Data Platform, Private Cloud, Licenses and Data Center.1 A Scope is a segment of spend aligned to a business construct such as a product or cost center, and it can draw from several categories.1

That matters for model spend because it rarely lives in one category. The FinOps for AI paper lists direct provider APIs (per token, under AI as token-based SaaS), cloud provider model services (on the cloud bill, under Public Cloud), embedded AI in SaaS products, GPU hours, and owned infrastructure as channels that can all feed one AI Scope.2 The same paper says most of the practice carries over. Cost is still price times quantity, cloud-billed AI shows up in FOCUS-format data, and tagging, allocation and commitments still apply. What changes is the unit (tokens, calls, provisioned throughput), volatile pricing, new stakeholders, and thin allocation data: direct model provider bills often lack native tagging, so allocation needs engineering instrumentation.2

This guide covers one slice: model spend on provider accounts and keys your company holds, where the provider invoices you directly and your gateway sits in the request path. It walks the capabilities that most often break first.

The three ledgers you reconcile

On customer-held keys, no single system holds the whole truth. You work with three records:

  1. The provider's invoice and cost API. This is what you owe. It is accurate and late, and it is usually grouped by provider project or key, not by your product features.
  2. The cloud bill, for anything bought through a cloud provider's model service. This is already in your cloud FinOps pipeline, often in FOCUS format.2
  3. The gateway request log. This is timely and carries your own dimensions, but its cost is a rate-table calculation made at request time, not an invoice.

An INFRO-style gateway makes the third ledger possible without changing the first: you connect provider accounts you already hold, your providers invoice you directly, and the gateway records what each request used and estimates what your provider will bill.3 The job of the capability map is to decide which ledger answers which question.

QuestionBest ledgerWhy
What do we owe this month?Provider invoice or cost APIIt is the invoiced amount
Which feature or customer drove it?Gateway request logOnly the application knows the feature and customer
Did something spike today?Gateway request logInvoices arrive after the fact
Is our estimate right?Both, compared dailyThe gap is a rate or coverage problem to fix
Which ledger answers which FinOps question

The capability map

The Framework groups capabilities under four domains: Understand Usage & Cost, Quantify Business Value, Optimize Usage & Cost, and Manage the FinOps Practice.1 The map below covers the capabilities a team extending cloud FinOps to model spend touches first.

Capability (domain)AI data sourceGateway field or endpoint
Data Ingestion (Understand)Provider cost APIs, cloud bill, request logFOCUS export of request-level usage
Allocation (Understand)Request metadata, key and project structureworkflow, feature, user_id, promoted tags, project, key, environment
Anomaly Management (Understand)Daily spend by scopeSpend anomaly, forecast and drift events
Planning & Estimating (Quantify)Token counts, rate tablesCost estimate before the request
Forecasting (Quantify)Units of work, calls per unit, tokens per callGET /v1/unit-economics drivers
Budgeting (Quantify)Forecast, hard capsBudgets per organization, project, member and key
Unit Economics (Quantify)Cost divided by outcomecost_per_run, per feature, per end user
Rate Optimization (Optimize)Contract rates, committed spendNegotiated rates and commitment tracking
Invoicing & Chargeback (Manage)Allocated cost by cost centerCost centers with rules and period history
Framework capability, AI data source, and the field that feeds it

Everything below follows from the first rows. If the request log cannot carry your dimensions, none of the later rows work.

Allocation: put the dimensions on the request

The Allocation capability asks for an allocation strategy, a tagging and hierarchy strategy, and a shared cost strategy, plus validation that the allocation is complete.4 It also describes shifting left: ownership and metadata enforced where a resource is created, not reconstructed in a later tagging cleanup.4 For AI, the "resource" is a request, so shifting left means the calling code sends the fields.

A gateway can carry them as reserved metadata. In INFRO's contract the reserved keys are workflow, trace_id, step, feature and user_id, and free-form tags; every request already carries project, gateway key, environment, model, provider and route.5 Values are validated: a malformed workflow, step or feature is refused with 400 invalid_attribution rather than dropped.5

attributed_call.py
from openai import OpenAI

client = OpenAI(base_url="https://api.infro.io/v1", api_key="INFRO_API_KEY")

resp = client.chat.completions.create(
    model="openai/gpt-5.6-sol",
    messages=[{"role": "user", "content": "Summarize this ticket"}],
    extra_body={
        "metadata": {
            "workflow": "support-agent",
            "trace_id": "run_8f2c",
            "feature": "summarize",
            "user_id": "cust_123",
            "tags": {"team": "support"},
        }
    },
)

Two behaviours shape your tagging policy. First, attribution applies from the request that first carries it; earlier requests stay unattributed and nothing is backfilled or guessed.5 Second, to group or match on a free-form tag you promote its key (up to five per organization), and only requests metered after promotion carry it; grouping by an unpromoted key returns 400 tag_not_promoted.5 Decide your five keys (team, cost code, product line) before launch, not after the first quarterly review.

For chargeback, cost center rules book estimated spend by first-match order on project, key, member, environment, workflow, feature, promoted tag or end-user prefix. What matches nothing is shown as Unallocated and never spread across other centers.6 Shared costs, such as a retrieval index used by three teams, can be split by fixed weights or in proportion to direct spend, and split lines are labelled as allocated.6 That is the Framework's shared cost strategy made explicit: you decide per shared item whether to allocate it or fund it centrally, the "informed ignore" choice the capability page describes.4 Rules are versioned by period, so a reorganization in October does not rewrite what September said.6 Showback mechanics are covered in Showback and chargeback for AI spend.

Anomaly management: scope the baseline

The Framework's Anomaly Management capability says detection should look at subcategories, not only aggregate usage, and that allocation metadata is critical both to detect anomalies and to know who can resolve them.7 Its Walk level includes forecast-breach alerts and automatic routing to responsible teams; Run adds integration with ticketing and event systems.7 It also warns that anticipated spikes, like a new environment launching, will trigger alerts, so owners should announce them and document the outcome.7

For model spend, the useful signals are the ones a daily invoice cannot give. INFRO's alert events illustrate the set:8

  • spend.anomaly: a scope is on course to spend far more than its usual day.
  • spend.forecast_over_budget: at the current rate a budget or key limit will be exceeded by at least 5% before it resets, with at least three days of a monthly period left.
  • cost.drift: on at least five of the last seven days the estimate leaned the same way, by more than 5%, from the cost the provider's own API reported. This needs cost reconciliation.
  • unpriced.traffic: for more than six hours, at least 5% of successful requests (and at least 20) had no price, so every spend figure is a lower bound.
  • traffic.model_changed and traffic.regression: output tokens per request, cache share, fallback share or latency moved with no error.

Map these to the Framework's KPIs rather than inventing new ones: count of anomalies, mean time to detect, mean time to notify the owner, and unresolved duration.7 Allocation fields decide the owner, so the alert for feature=summarize goes to the team that owns it. See five LLM spend anomalies for the shapes these take.

Forecasting: drivers, not trend lines

The Framework describes forecasting as a model of future spend for a scope, built from historical spending, planned changes and lifecycle effects, feeding Budgeting. Its Run level combines rolling, trend-based and driver-based models and aligns forecasts to the same allocation constructs used for reporting.9 A pure trend line fails on AI spend because a model swap, a longer prompt or a lost cache changes the rate without changing the volume.

A driver-based model splits spend into units of work, calls per unit, and tokens per call, each owned by someone. The request log gives you the last two; the product plan gives you the first.

Two inputs make this more accurate. Rates should be your contract rates, not list rates; INFRO lets you enter negotiated rates so estimates use them before the vendor's list rate. Committed-spend agreements can be recorded and tracked against reported cost with an end-of-term forecast, which feeds the rate side of the model. For planning before launch (Planning & Estimating), a cost estimate for a request on your own provider account gives the per-call figure without sending traffic. Budgets then turn the agreed forecast into a ceiling at organization, project, member or key level, which is where the Framework hands Forecasting off to Budgeting.9 A longer method is in AI budget planning for 2027.

Unit economics: from cost per token to cost per outcome

The Framework separates resource efficiency metrics (cost per token) from business unit metrics (cost per tenant, per case resolved), and says early generative AI unit economics usually starts at cost per token and moves toward cost per assist, per agent action or per case deflected.10 The FinOps for AI paper adds two rules worth adopting: measure the use case rather than the token, and report cost per successful outcome as a range.2

The denominator is what your application records. The numerator is allocated estimated cost. INFRO's unit economics endpoint groups by workflow, feature, end_user or cost_center and returns requests, runs, estimated cost, cost per request, and median and p90 cost per run, where a run is one (workflow, trace_id) pair.11

Shell
curl "https://api.infro.io/v1/unit-economics?by=feature&period=2026-10" \
  -H "Authorization: Bearer $INFRO_API_KEY"

Read the unpriced_requests and unpriced_share fields beside every figure. Cost per request divides by priced requests only, so a partial number never reads as a whole one, and requests without the dimension appear in a separate unattributed row.11 Percentiles matter because agent runs have fat tails; a median alone hides the runs that blow the budget. Quality still needs its own measure: a cheap run that fails is not a cheap outcome, as covered in cost per successful task.

Landing gateway data beside cloud cost

The FinOps for AI paper notes that cloud-billed AI already arrives in FOCUS format.2 To put gateway-observed spend in the same dataset, INFRO exports a FOCUS v1.4 Cost and Usage dataset from GET /v1/usage/focus, broken down by project, key, environment, model, provider, connection, route and your metadata tags.12

The important design decision is where the estimate goes. FOCUS requires BilledCost to reflect amounts as invoiced by the invoice issuer, not estimated values. Because the provider, not INFRO, invoices you, the per-request estimate is written to ListCost and ContractedCost, and BilledCost and EffectiveCost are populated only from figures your provider's own cost API reported.12 Two modes follow:

  • cost_basis=estimated (the default) covers every provider-day, omits BilledCost and EffectiveCost, and reports conformance as partial.12
  • cost_basis=reconciled requires charge_period=day, includes only provider-days with a reported figure, and needs a billing credential, available for OpenAI and Anthropic only.12
Shell
curl "https://api.infro.io/v1/usage/focus?cost_basis=reconciled&charge_period=day" \
  -H "Authorization: Bearer $INFRO_API_KEY"

If your FinOps platform sums BilledCost, expect gaps for providers without a cost API, and do not backfill them with estimates. Keep estimated and reconciled rows distinguishable in your warehouse. Reconciliation mechanics are in Reconciling estimated LLM spend with provider invoices.

A rollout order by maturity

The Framework's Crawl, Walk, Run model suits this extension.1 A workable order:

  • Define the AI Scope and its owners, including who fills the Engineering persona for AI products.
  • Fix the allocation taxonomy: workflow names, feature names, and the five promoted tag keys.
  • Make the metadata a code-review requirement for any new call site.
  • Book Unallocated to a named owner and track its share weekly.
  • Turn on daily reconciliation where the provider offers a cost API, and review drift findings.
  • Route spend anomaly and forecast alerts to the owning team, not only to the central FinOps channel.
  • Build the driver-based forecast for the top three workflows and report it as a range.
  • Publish cost per run or per outcome with the unpriced share beside it.

Start with the metadata. Every later capability, from anomaly routing to chargeback to unit cost, reads it.

Questions readers ask

Should AI be its own FinOps Scope or sit inside public cloud?
The FinOps for AI paper says model APIs, cloud services, SaaS and developer tools, GPUs and data centers can all feed one AI Scope, so you do not have to pick one category.2 The practical test is whether the people accountable for the spend look at it together. If they do, define one AI Scope and let it draw from several categories.
Who owns AI allocation: FinOps or engineering?
Both, in different roles. The paper notes that new SKUs and direct provider bills often lack native tagging, so allocation needs engineering instrumentation, and that data scientists and ML engineers act in the Engineering persona.2 FinOps defines the allocation taxonomy; engineering sends the fields on each request.

From the team that builds it

Where this shows up in INFRO

INFRO is a control plane in front of the provider accounts you already hold. The capabilities below are the parts of it this article touches, each with the documentation that defines its behaviour.

  • Spend attribution

    Available with a plan

    Group cost by model, project, key, or an end-user id you attach to the request.

    Read the documentation for Spend attribution
  • Usage, request and FOCUS exports

    Available with a plan

    GET /v1/usage and GET /v1/requests on any gateway key, the request log and usage series as CSV, plus a FOCUS v1.4 Cost and Usage dataset as JSON or CSV, so AI spend lands in your FinOps platform beside the rest of your cloud cost.

    Read the documentation for Usage, request and FOCUS exports
  • Usage and cost per request

    Available with a plan

    Every request records its model, latency, token or unit counts, and estimated provider cost, queryable by project and key.

    Read the documentation for Usage and cost per request
  • Spend anomaly and drift alerts

    Available with a plan

    Each scope's usual day is learned from its own history; a day that departs from it, a budget forecast to be exceeded, cost estimates drifting from the provider's own figures, unpriced traffic and failing connections become findings in the console. Routed to email, Slack and signed webhooks on every plan.

    Read the documentation for Spend anomaly and drift alerts
  • Budgets and spend ceilings

    Available with a plan

    A hard cap per organization, project, member, and key, with alerts at your own thresholds.

    Read the documentation for Budgets and spend ceilings
  • Provider commitment tracking

    Available with a plan

    Record a committed-spend agreement with a provider and track it against reported cost, with a forecast to the end of the term. Included on every plan.

    Read the documentation for Provider commitment tracking
  • Provider cost reconciliation

    Available with a plan

    Daily comparison of estimated spend against the cost reported by OpenAI's and Anthropic's own cost APIs, using a separate admin credential, with the likely cause of a persistent gap and a suggested rate you can apply. Included on every plan.

    Read the documentation for Provider cost reconciliation
  • Negotiated provider rates

    Available with a plan

    Enter the rates your contracts actually carry, per model and optionally per provider, so estimated cost uses them before the vendor's list rate. Included on every plan.

    Read the documentation for Negotiated provider rates

INFRO accounts are self-serve. Provider usage is billed to you by your providers; INFRO charges a software subscription and takes 0% of model spend. See plans.

Sources

Numbered in order of first citation. Each was opened and checked against the claim on the date shown.

  1. 1.FinOps Framework Overview (opens in a new tab) — FinOps Foundation. Accessed Nov 15, 2026.
  2. 2.FinOps for AI Overview (opens in a new tab) — FinOps Foundation. Accessed Nov 15, 2026.
  3. 3.INFRO documentation overview (opens in a new tab) — INFRO. Accessed Nov 15, 2026.
  4. 4.Allocation FinOps Framework Capability (opens in a new tab) — FinOps Foundation. Accessed Nov 15, 2026.
  5. 5.Cost attribution (opens in a new tab) — INFRO. Accessed Nov 15, 2026.
  6. 6.Cost centers (opens in a new tab) — INFRO. Accessed Nov 15, 2026.
  7. 7.Anomaly Management FinOps Framework Capability (opens in a new tab) — FinOps Foundation. Accessed Nov 15, 2026.
  8. 8.Alerts (opens in a new tab) — INFRO. Accessed Nov 15, 2026.
  9. 9.Forecasting FinOps Framework Capability (opens in a new tab) — FinOps Foundation. Accessed Nov 15, 2026.
  10. 10.Capability: Unit Economics (opens in a new tab) — FinOps Foundation. Accessed Nov 15, 2026.
  11. 11.Unit economics API reference (opens in a new tab) — INFRO. Accessed Nov 15, 2026.
  12. 12.FOCUS export (opens in a new tab) — INFRO. Accessed Nov 15, 2026.

About this article

Read on 2026-11-15: the FinOps Framework overview, the FinOps for AI overview, the Allocation, Anomaly Management, Forecasting and Unit Economics capability pages, and the INFRO docs pages on the overview, FOCUS export, cost attribution, cost centers, unit economics and alerts. Several pages were returned truncated, so anything beyond the text shown (later maturity rows, KPI definitions) was left out; provider cost API details and INFRO reconciliation and commitment docs were not read and are described only at capability level.

Last checked against its sources on . The next review is due by . No separate named reviewer is recorded for this article.

How articles are written, sourced and corrected is set out in the editorial standards.