Assessment · Governance · Cost within the governance envelope

16Budgets, caps and spend guardrails

What stops a bad prompt or loop from running up the bill?

Monthly budgets, daily limits and per-run caps set where AI traffic flows.

AutomatedStakeholder interviews 2 controls 3 engines

How we collect

  • AutomatedSpend by team, workload and agent from gateway and billsRuns today
  • Stakeholder interviewsFinance: budgets and who gets the alertRuns today

Status labels show what runs today, what needs an export or setup from you, and what is planned.

What you get

  • Budget, quota, rate limit and circuit breaker told apart
  • Vendor cap gaps (Azure OpenAI has no simple hard budget limit)
  • Runs that would have breached a cap

Questions we ask

  • Who gets the alert when a budget is close?

We can start from

Budgets from your FinOps tool

Data sources

SourceWhat we readStatus
AI gateway telemetryLiteLLM, Cloudflare AI Gateway or AICost CostWall logs: cost per team, workload, agent and outcome.Partly automated
QuestionnaireThe short interview for what data cannot show: purpose, owners, decisions AI informs, regulations in scope.Runs today
OpenAI Usage and Costs APIOrganization usage and cost by project and model, read with an Admin API key.Wave 2
Anthropic Usage and Cost APIToken usage by model, workspace and API key, and daily cost, read with an Admin API key.Wave 2

Built on governance engine modules

P6 LiveAI Cost Governance & FinOps

What does AI cost you, and who is accountable for it?

Value & Optimization

AICost governance controls in this module

AICost-GovControl502Runs today
Budgets, caps and spend guardrails
What it is

Monthly budgets, daily hard limits, per-run caps, retry and context limits, and approval before spend above a threshold.

Why it is needed

AI cost moves with usage. Without caps, one loop or one long-context workload can exceed a month of budget.

Why enterprises need it

Enterprises want predictable AI bills and the ability to stop runaway spend without stopping the business.

What you get:Predictable monthly AI spendRunaway workloads stopped automaticallyLimits enforced where traffic flows
Run by
AI Cost Governance and FinOps engineCost Firewall engineBudget Planner engineAgent Cost Reserve engineRetry Waste engine
Data
AI gateway telemetry, Questionnaire
Evidence produced
Guardrail table: workload, monthly budget, daily limit, per-run cap, enforcement point, last breach.
Maps to
FinOps Framework; NIST AI RMF: Manage
AICost-GovControl503Runs today
Cost anomaly and runaway agent detection
What it is

Detection of unusual spend: loops, retries, context growth, new models and sudden usage spikes, with an alert and an owner.

Why it is needed

Cost spikes are often the first sign of a broken agent, an abused key or a misconfigured workload.

Why enterprises need it

Teams want to hear about it the same day, not from the invoice next month.

What you get:Same-day alerts on spikesBroken agents found through costAbused keys spotted early
Run by
AI Cost Governance and FinOps engineAgent Loop engineRetry Waste engineContext Size Cost engine
Data
AI gateway telemetry, OpenAI Usage and Costs API, Anthropic Usage and Cost API
Evidence produced
Anomaly log: date, workload, expected cost, actual cost, cause, action, owner.
Maps to
FinOps Framework; NIST AI RMF: Measure

Frameworks

FinOps Framework and FOCUSCost visibility, allocation, budgets, forecasting and unit economics for AI

Stakeholders

CFOFinOps
📖 Data sources & methodology 172 text models · 9 embeddings · 44 vision · 62 audio · 8 vector DBs across 10 vendor pages · last verified 2026-10-18

Methodology

  • All prices are USD per 1 million tokens, current as of 2026-10-18.
  • Vendor-published values have no mark. Inferred/extrapolated values are marked with * and listed below.
  • Batch API discounts are 50% off standard rates across providers that offer Batch mode.
  • Prompt caching discounts vary by provider (typically 80-90% off cached input tokens).
  • Regional data-residency surcharges (Anthropic 1.1x, OpenAI 1.1x, Google regional tiers) are NOT included in base rates.
  • Long-context pricing tiers apply when input exceeds model threshold.
  • Embedding prices are input-only (no output tokens generated).

Primary sources

Last-verified date is the most recent successful daily snapshot (aicost_pricing_snapshots) or, when no snapshot exists yet, the latest successful crawler run (aicost_crawler_runs). 10 of 10 vendors are currently verified. Aggregator services (TokenCost, AI Pricing Guru, etc.) are not listed.

Anthropic
2026-10-18
https://www.anthropic.com/pricing
Daily snapshot since Sep 2023 · 704 days captured
Anthropic Docs
2026-10-18
https://platform.claude.com/docs/en/about-claude/pricing
Daily snapshot since Sep 2023 · 704 days captured
OpenAI
2026-10-18
https://openai.com/api/pricing/
Daily snapshot since Sep 2023 · 705 days captured
Google AI
2026-10-18
https://ai.google.dev/gemini-api/docs/pricing
Daily snapshot since Dec 2023 · 680 days captured
Google Vertex
2026-10-18
https://cloud.google.com/vertex-ai/generative-ai/pricing
Daily snapshot since Dec 2023 · 680 days captured
DeepSeek
2026-10-18
https://api-docs.deepseek.com/quick_start/pricing
Daily snapshot since May 2024 · 619 days captured
xAI
2026-10-18
https://x.ai/api
Daily snapshot since Nov 2024 · 537 days captured
Mistral
2026-10-18
https://mistral.ai/pricing
Daily snapshot since Dec 2023 · 678 days captured
Cohere
2026-10-18
https://cohere.com/pricing
Daily snapshot since Sep 2023 · 704 days captured

Inferred values (marked with * in calculator tables)

Derived from industry conventions, not directly published by the vendor. Typical conventions: cached input = 10% of base (90% off), Batch API = 50% of base (50% off).

Vendor / Model Field Why it’s inferred
Anthropic — Claude Sonnet 4.6 cachedInput Derived at 10% of input rate — Anthropic publishes 90% cache-hit discount on this tier.
Anthropic — Claude Sonnet 4.5 cachedInput Derived at 10% of input rate; same 90% cache-hit convention as Sonnet 4.6.
Anthropic — Claude Sonnet 4.5 batchInput Derived at 50% of standard input — Anthropic documents uniform 50% Batch discount.
Anthropic — Claude Sonnet 4.5 batchOutput Derived at 50% of standard output — Anthropic documents uniform 50% Batch discount.
Anthropic — Claude Haiku 4.5 cachedInput Derived at 10% of input rate — Anthropic 90% cache-hit discount convention.
OpenAI — GPT-5.4 Mini cachedInput Derived at 10% of input — OpenAI documents automatic 90% discount on cache hits across GPT-5.x tier.
OpenAI — GPT-5.4 Nano cachedInput Derived at 10% of input — OpenAI 90% cache-hit convention.
OpenAI — GPT-5.4 Nano batchInput Derived at 50% of input — OpenAI Batch API uniform 50% discount.
OpenAI — GPT-5.4 Nano batchOutput Derived at 50% of output — OpenAI Batch API uniform 50% discount.
OpenAI — GPT-5.4 Pro cachedInput Derived at 10% of input — OpenAI 90% cache-hit convention.
OpenAI — GPT-5.4 Pro batchInput Derived at 50% of input — OpenAI Batch API uniform 50% discount.
OpenAI — GPT-5.4 Pro batchOutput Derived at 50% of output — OpenAI Batch API uniform 50% discount.
OpenAI — GPT-5.2 cachedInput Derived at 10% of input; no residency uplift.
OpenAI — GPT-5.2 batchInput Derived at 50% of input.
OpenAI — GPT-5.2 batchOutput Derived at 50% of output.
OpenAI — GPT-5 cachedInput Derived at 10% of input.
OpenAI — GPT-5 batchInput Derived at 50% of input.
OpenAI — GPT-5 batchOutput Derived at 50% of output.
OpenAI — GPT-5.5 Pro cachedInput Derived at 10% of input — OpenAI does not publish a cached rate for *-pro models; using the family convention.
OpenAI — GPT-5.5 Pro batchInput Derived at 50% of input.
OpenAI — GPT-5.5 Pro batchOutput Derived at 50% of output.
OpenAI — GPT-5.2 Pro cachedInput Derived at 10% of input — pro-tier convention.
OpenAI — GPT-5.2 Pro batchInput Derived at 50% of input.
OpenAI — GPT-5.2 Pro batchOutput Derived at 50% of output.
OpenAI — GPT-5.1 batchInput Derived at 50% of input.
OpenAI — GPT-5.1 batchOutput Derived at 50% of output.
OpenAI — GPT-5 Pro batchInput Derived at 50% of input.
OpenAI — GPT-5 Pro batchOutput Derived at 50% of output.
OpenAI — GPT-5 Nano cachedInput Derived at 10% of input.
OpenAI — GPT-5 Nano batchInput Derived at 50% of input.
OpenAI — GPT-5 Nano batchOutput Derived at 50% of output.
Google — Gemini 3 Flash cachedInput Derived at 10% of input — Google caching discount convention ~90%.
Google — Gemini 3.1 Flash-Lite cachedInput Derived at 10% of input — Google caching convention.
Google — Gemini 3.1 Flash-Lite batchInput Derived at 50% of input — Google Batch API uniform 50% discount.
Google — Gemini 3.1 Flash-Lite batchOutput Derived at 50% of output — Google Batch API uniform 50% discount.
Google — Gemini 2.5 Pro cachedInput Derived at 10% of input.
Google — Gemini 2.5 Flash cachedInput Derived at 10% of input.
Google — Gemini 2.5 Flash-Lite cachedInput Derived at 10% of input — Google caching convention.
Google — Gemini 2.5 Flash-Lite batchInput Derived at 50% of input — Google Batch API uniform 50% discount.
Google — Gemini 2.5 Flash-Lite batchOutput Derived at 50% of output — Google Batch API uniform 50% discount.
xAI — Grok 4 (legacy) cachedInput Extrapolated at 25% of base.

Pricing is cross-verified against the LiteLLM community registry when available. Daily snapshots are kept in aicost_pricing_snapshots; every change is logged to aicost_price_changelog with old & new values for full audit trail. Read the full methodology →