UK-based independent AI efficiency projectEvidence before claims ยท 2026

API Cost Scenario: Keep Inputs, Rates, FX Date and Limits Visible

CALCULATED SCENARIO METHOD ยท NOT ACTUAL SPEND

API Cost Scenario: Keep Inputs, Rates, FX Date and Limits Visible

A long-scroll visual companion to the article. It summarizes the article evidence boundary and method; it does not extend the underlying result.

At a glance

API Cost Scenario: Keep Inputs, Rates, FX Date and Limits VisibleFour-step visual: INPUT / CACHE / OUTPUT; DATED RATE SOURCE; FX DATE / CURRENCY; CALCULATED ESTIMATE. A calculator scenario is calculated from entered assumptions; it is not a record of actual provider spend.CALCULATED SCENARIO METHOD ยท NOT ACTUAL SPEND1INPUT / CACHE / OUTPUT2DATED RATE SOURCE3FX DATE / CURRENCY4CALCULATED ESTIMATEEvidence labels and limits travel with the visual.
A useful estimate preserves the usage denominator, provider rate unit, billing currency, FX date, and exclusions.

Evidence in scope

  • Label every quantity and unit
  • Keep rate and FX dates visible
  • Separate scenario from observed spend

Evidence boundary: A calculator scenario is calculated from entered assumptions; it is not a record of actual provider spend.

How to use the diagram

Enter distinct token fields, dated official prices, currency/FX source, expected retries, and the workload window; label assumptions.

What this visual explains: A useful estimate preserves the usage denominator, provider rate unit, billing currency, FX date, and exclusions.

What it does not establish

No current estimate is asserted for a real workload. Refresh official rates and FX sources before publishing dated values.

โ† View article ยท Return to source article