Skip to content

Use casesFinOps for AI

Every AI request, attributed before the invoice arrives.

Every request is recorded with its model, project, key and estimated provider cost at your own rates. Group it by the team, feature or customer that caused it, compare it with what the provider reports, and send it to the FinOps tools you already use.

Start 14-day trialRequest a demo
Estimated provider cost · October · group by featureExample
summarize$1,284.10 · 41%
search$902.55 · 29%
support-agent$688.20 · 22%
unattributed$251.40 · 8% · no feature sent

Example organization. Estimated provider cost, billed to you by your providers; INFRO's subscription is separate.

The problem

Without a control plane

  • One invoice per provider, and no line that says which team caused it.
  • List prices in every estimate, while your contract carries other rates.
  • AI spend sits outside the FinOps platform that holds the rest of cloud cost.

With INFRO

  • Cost grouped by project, key, member, feature or end customer.
  • Your negotiated rates used before the vendor's list rate.
  • A FOCUS dataset and usage APIs for the tools you already run.

How it works

  1. Tag at the source

    Projects and keys attribute every request automatically; X-INFRO-Feature and X-INFRO-User-Id add the product feature and the end customer.

  2. Price it with your rates

    Enter the rates your contracts carry, per model and per provider. Estimates use them before the list rate; anything with no known price is shown as unpriced, never $0.

  3. Close the loop

    Compare estimates with the cost the provider reports, track commitments, and export the result as FOCUS or through the usage API.

What you get

Each one is documented, and each says which plan includes it. Where no plan is named, it is on every plan.

  • Spend attribution

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

    Docs

  • Your negotiated ratesFrom Team

    Enter the rates your contracts carry so estimates use them before the vendor's list rate.

    Docs

  • ReconciliationFrom Business

    Daily comparison of estimated spend with OpenAI's and Anthropic's own cost APIs, with the likely cause of a gap.

    Docs

  • Cost centers and statementsFrom Team

    Rules assign requests to the centers finance charges back to; a monthly statement totals each one.

    Docs

  • FOCUS and usage exports

    GET /v1/usage and /v1/requests, CSV from the console, and a FOCUS v1.4 dataset for your FinOps platform.

    Docs

  • Summary and monthly report

    Spend against budget and its projection on one page, emailed every Monday, with a printable monthly report.

    Docs

Who it is for

  • FinOps practitionersAI spend in the same FOCUS shape as the rest of your cloud cost, attributed before month end.
  • Finance leadersShowback or chargeback by team on numbers that use your contract rates.
  • Engineering managersWhich feature, model or key moved the number this week, without a spreadsheet.

FAQ

Is the cost INFRO shows what my provider will bill?

It is an estimate of provider cost, from list rates or the negotiated rates you entered. Your provider's invoice is the final figure. Where OpenAI or Anthropic publish cost data, reconciliation compares the two daily.

Does INFRO add anything to my model spend?

No. 0% markup: your providers bill you directly for inference, and INFRO bills a separate software subscription. The two are never added together on any INFRO screen.

Which FinOps tools can read the export?

Any tool that loads a FOCUS v1.4 Cost and Usage dataset as CSV or JSON, or anything that can call the usage API with a gateway key.

The full contract is in the Cost attribution docs, and every other question is on the FAQ.

Field guides

Related

All use cases

Get started

Try it on your own provider accounts.

Connect a provider, create a gateway key and change one base URL. Your providers keep billing you directly; 0% markup on model spend.

Start 14-day trialRequest a demo