AI Cost per Request Calculator

Divide an AI cost you already know by the requests it covered.

In short

Formula: Cost per request = Total AI cost / Requests

Complete the required fields to see the result.

What this calculator does

The FinOps unit-economics definition applied with the request as the unit. The figure is shown per thousand requests because a per-request figure usually rounds away.

Use it to turn Currency, Total AI cost for the period, Requests in the period, Price as of (optional), and the other shown inputs into a checked result you can compare, copy, or rerun with different assumptions.

The page shows the formula, a numeric worked example, and the assumptions that affect this professional & industry calculation.

Inputs and what they mean

Currency: — Amounts are shown in the currency you pick. No exchange rate is applied..
Total AI cost for the period: — Everything you are spreading over the requests..
Requests in the period: — Model calls served in the same period..
Price as of (optional): — The date you took these prices. It is shown with the result so the figure is never read as a current vendor price..
Price source (optional): — Where the prices came from. Shown with the result..

How to use it

Enter your own figures — the calculator never fills in a rate, price or benchmark for you.
Press Calculate to see the result.
Read the formula, variables, assumptions and source below the result before you rely on it.

Formula

Cost per request = Total AI cost / Requests.

Inputs used: Currency, Total AI cost for the period, Requests in the period, Price as of (optional), Price source (optional).

Edge handling: Total AI cost for the period is required.; Total AI cost for the period cannot be negative.; Total AI cost for the period must be no more than 1000000000000.; Requests in the period is required.; Requests in the period cannot be negative..

Worked example

$8,400 across 1.25 million requests

Start with Currency: USD, Total AI cost for the period: 8400, Requests in the period: 1250000.
Apply the method: Cost per request = Total AI cost / Requests.
Shown per thousand requests, because a per-request figure rounds to nothing.

Reading the result

The headline figure is the main answer. Any breakdown underneath shows the parts that make it up, so you can check the working and see what changes when you adjust an input.

Limitations and assumptions

Inputs outside the supported range are rejected rather than forced into a result.
The result depends on the values you enter for this ai cost per request calculator; it does not supply missing rates, rules, prices, dates, or assumptions for you.

Reference: The Linux Foundation — Unit economics — FinOps Framework

Last reviewed: September 17, 2026

Common questions

Where does this formula come from?

FinOps Framework capability: unit economics — cost per business unit is total cost for a period divided by the units delivered in the same period; a workload's cost is the sum of its metered components charged at the rates the organisation actually pays. See the source link on this page.

What kind of calculation is this?

A unit cost: total AI cost for a period over the requests served in the same period. Check the formula, example, and limitations on this page before using the result for a real professional & industry decision.

What are its limits?

Arithmetic over the figures entered — it cannot tell whether the metering, logs or invoices behind them are complete. The result is only as current as the rates entered; a rate taken months ago is not a current price. Tiered, committed-use, cached-input and minimum-spend pricing are not modelled unless the user has already reduced them to the rates entered. A unit cost hides the mix behind it: a change in average request size moves the figure without any price changing.

How do I use the AI Cost per Request Calculator?

Enter the required values for Currency, Total AI cost for the period, Requests in the period, Price as of (optional), Price source (optional). The calculator applies the formula on this page and shows the main result with any supporting breakdown so you can check the arithmetic.

What formula does the AI Cost per Request Calculator use?

Cost per request = Total AI cost / Requests The visible formula section above lists the calculation path and the edge cases the page handles, so the result can be checked without relying on the form alone. Check the formula, example, and limitations on this page before using the result for a real professional & industry decision.

Can the AI Cost per Request Calculator be used for exact decisions?

Use it as a calculation aid, not as a substitute for checking the underlying rule, contract, policy, or professional advice that applies to your situation. When a result depends on local rules, personal details, prices, or dates, enter those values yourself and confirm them before acting.

Formula, source and verification

A unit cost: total AI cost for a period over the requests served in the same period.

The question it answers: What does one request or one customer cost us in AI, and does the revenue cover it?

The formula

Cost per request = Total AI cost / Requests

C — Total AI cost: (currency). The whole cost being spread.
n — Requests: (requests). Requests served in the same period.

Units: Currency and requests in, currency per thousand and per million requests out.

What kind of calculation this is

Business input model. The answer depends on business figures only you can supply, such as your own costs, rates or volumes. No market or benchmark values are assumed for you.

Method

The FinOps unit-economics definition applied with the request as the unit. The figure is shown per thousand requests because a per-request figure usually rounds away.

Assumptions built into the result

Mathematical: All the figures entered cover the same measurement period.
Mathematical: Token counts, requests and hours are taken from the user's own logs or bill.
Mathematical: The cost and the request count cover the same period and the same scope.

Figures this calculator will never guess for you

No target, benchmark, industry average or typical figure is supplied for any value.
A definition is never presented as a goal: a cost per request is not a target cost per request, and a contribution margin is not a target margin.
No model price, GPU price, rate card or list price is built in; every amount is entered by the user.
No token count, context length or output length is assumed on the user's behalf.
No currency conversion is applied; amounts stay in the currency selected.

Limitations

Arithmetic over the figures entered — it cannot tell whether the metering, logs or invoices behind them are complete.
The result is only as current as the rates entered; a rate taken months ago is not a current price.
Tiered, committed-use, cached-input and minimum-spend pricing are not modelled unless the user has already reduced them to the rates entered.
A unit cost hides the mix behind it: a change in average request size moves the figure without any price changing.

Source and version

Standard or reference: FinOps Framework — unit economics and workload cost — FinOps Foundation (FinOps Framework capability: unit economics — cost per business unit is total cost for a period divided by the units delivered in the same period; a workload's cost is the sum of its metered components charged at the rates the organisation actually pays.)
Published source: The Linux Foundation — FinOps Framework
Formula version: Version 1
Verification: Reviewed against the cited source on 2026-09-17
How much weight the source carries: Standards or government
Applies to
Currency: Amounts stay in the currency you choose; no exchange rate is applied.