Assessment · Governance · Run continuously

18Executable policy

How do our rules actually run, not just sit in a document?

Cost and governance rules compiled into policy your own gateway or cloud enforces. AICost stays out of the request path unless you choose the enforcing proxy.

AutomatedStakeholder interviewsUses your existing assessments 3 controls 3 engines

How we collect

  • AutomatedGateway and cloud configs read to see what is enforced todayNeeds your export or setup
  • Stakeholder interviewsDecisions, not policies: 25 questions on data, agents, tools and oversightRuns today
  • Uses your existing assessmentsPolicies from your GRC tool turned into rulesPlanned

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

What you get

  • Gap between written policy and enforced policy

Questions we ask

  • Which gateway or cloud console do you use?

We can start from

Policy documents you already have; we turn them into decisions and rules

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
Microsoft Graph and Entra IDService principals, OAuth grants, app registrations, sign-ins to AI apps, Copilot usage reports. Read-only scopes, metadata only.Runs today

Built on governance engine modules

P6 LiveAI Cost Governance & FinOps

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

Value & Optimization
P14 PlannedPrivacy, Confidentiality & IP

Whose data trains what, and who owns the output?

Assess & Govern

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-GovControl402Runs today
Limits on what agents can do
What it is

Rules for agent actions: which tools, which data, how many steps, how much spend, which actions need a person, and a tested stop switch.

Why it is needed

Agents act, not only answer. A loop or a wrong tool call can change records or run up a bill in minutes.

Why enterprises need it

Before giving agents more autonomy, teams need hard limits that hold even when the model misbehaves.

What you get:Bounded actions and spend per runHuman approval on consequential stepsA stop switch that is tested
Run by
Agents, MCP and Autonomous Actions engineAgent Access Limits engineCost Firewall engineAgent Loop engineCost per Agent Run engine
Data
AI gateway telemetry, Microsoft Graph and Entra ID, Questionnaire
Evidence produced
Agent limits table: agent, tools allowed, data allowed, max steps, max cost per run, approval points, stop test date.
Maps to
NIST AI RMF: Manage; OWASP Top 10 for LLM: excessive agency
AICost-GovControl304Runs today
Data residency and model origin
What it is

Where each model runs and where its provider is based, matched to your residency and sovereignty rules.

Why it is needed

Some data cannot leave a region, and some buyers will not accept models from certain jurisdictions.

Why enterprises need it

Public sector, health and finance buyers ask for this in every security review.

What you get:Allowed regions per data classModel origin risk knownApproved routes for sensitive work
Run by
Privacy Decision engineAI Architecture Decision engineModel Origin Risk engineLocal or Cloud engine
Data
Questionnaire, AI gateway telemetry
Evidence produced
Residency table: system, data class, model, provider country, processing region, allowed or blocked.
Maps to
GDPR transfers; Sector sovereignty rules

Frameworks

GDPR and CCPA/CPRALawful basis, minimization, transfers, retention, explanation duties
OWASP Top 10 for LLMPrompt injection, data leakage, excessive agency, supply chain
FinOps Framework and FOCUSCost visibility, allocation, budgets, forecasting and unit economics for AI

Stakeholders

AI platform ownerCISOCompliance
AICost.ai pricing data keeps our calculations accurate across top AI and cloud vendors · last updated 2026-10-22

Methodology

  • All prices are USD per 1 million tokens, current as of 2026-10-22.
  • 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-22
https://www.anthropic.com/pricing
Daily snapshot since Sep 2023 · 708 days captured
Anthropic Docs
2026-10-22
https://platform.claude.com/docs/en/about-claude/pricing
Daily snapshot since Sep 2023 · 708 days captured
OpenAI
2026-10-22
https://openai.com/api/pricing/
Daily snapshot since Sep 2023 · 709 days captured
Google AI
2026-10-22
https://ai.google.dev/gemini-api/docs/pricing
Daily snapshot since Dec 2023 · 684 days captured
Google Vertex
2026-10-22
https://cloud.google.com/vertex-ai/generative-ai/pricing
Daily snapshot since Dec 2023 · 684 days captured
DeepSeek
2026-10-22
https://api-docs.deepseek.com/quick_start/pricing
Daily snapshot since May 2024 · 623 days captured
xAI
2026-10-22
https://x.ai/api
Daily snapshot since Nov 2024 · 541 days captured
Mistral
2026-10-22
https://mistral.ai/pricing
Daily snapshot since Dec 2023 · 682 days captured
Cohere
2026-10-22
https://cohere.com/pricing
Daily snapshot since Sep 2023 · 708 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 →