AI agent cost governance is the set of controls that attributes token spend to an agent, a workflow and a named owner, measures cost per completed task, and enforces budgets while agents run. A monthly invoice review cannot do that job, because it reports on decisions software already made weeks earlier. In October 2026, three vendors announced or shipped cost controls inside their agent governance and SaaS management products, next to identity and policy.
Here is what the three vendors announced. Only BetterCloud's is confirmed available today. Google and ServiceNow named this quarter for some items, so read the status column closely.
| Vendor | What was announced | Stated availability |
|---|---|---|
| Google Cloud Agent Gateway (Oct 22) | Token management to attribute spend, enforce budget guardrails and provide a single source of truth for token metrics, plus model routing policies | "Coming this quarter in preview." The product documentation says support is coming soon and that features and timing may change. No GA date. |
| ServiceNow (Oct 15) | Cost governance by user, department and runtime; AI Cost Management in IT Asset Management, combining frontier model, embedded SaaS AI, hyperscaler and data center GPU costs; policy enforcement managing alert-to-throttle-to-block responses | AI Passport, shadow AI detection and AI Cost Management expected in Q4 2026. The release gives no separate date for policy enforcement or cost governance. |
| BetterCloud (Oct 29) | AI consumption across providers in one view, monthly cost and owner per tool, total AI spend per employee, and agent lifecycle management | Available now to BetterCloud customers, according to the company's release. More providers are planned. |
Each sees a different slice: a gateway sees traffic through it, a SaaS management platform sees tools and people, and an asset view tries to combine them. Demand is clear: in the State of FinOps 2026 report, 98% of respondents said they manage AI spend, up from 31% two years earlier, and the top-ranked tool capability they asked for was granular monitoring of AI spend across tokens, LLM requests and GPU utilization.
An invoice answers "how much did we pay this provider?" Governance has to answer three harder questions.
Our earlier piece on agent economics covered why falling model prices do not lower the full cost of a production agent. Cheaper tokens also invite more agents and more background work, which is what makes governance urgent.
Every model and tool call should carry five tags: agent identity, workflow, business owner, cost center and environment. Give each agent its own identity and credential, because shared keys make attribution impossible. An AI gateway is the natural place to apply them. Google's pre-release documentation is a useful reference: it describes grouping usage by project, application, agent identity, model endpoint, API key or custom header, with anything unmatched recorded in a separate group.
That leftover bucket is your first KPI. Track unattributed spend as a percentage of total AI spend and drive it down. Embedded SaaS AI and per-seat licenses never cross your gateway, so those figures must come from billing data or a SaaS management tool.
Use cost per completed task: total model, tool and human review cost for a period, divided by the tasks finished to an accepted standard. Failed runs and retries stay in the numerator and out of the denominator.
Illustrative example, not client data: an invoice-coding agent makes 12,000 attempts in a month for $3,600 in model and tool cost, or $0.30 per run. People review 1,800 of those at $4.50 of labor each ($8,100), and 1,200 fail outright. Total cost is $11,700 for 10,800 accepted invoices, or about $1.08 per completed task. That is 3.6 times the per-run figure.
Use graduated enforcement, so most overruns end in a conversation and few end in an outage. ServiceNow uses alert-to-throttle-to-block to describe policy enforcement, and we apply that language to budgets. We add a separate security stop, because a compromised agent should not wait for a budget threshold.
| Stage | Illustrative trigger | What happens | Who acts |
|---|---|---|---|
| Alert | 60 to 80% of budget | Notify the owner and finance. No change in behavior. | Agent owner |
| Throttle | 90% of budget, or abnormal burn rate | Reduce concurrency, queue low-priority work, shift tested task types to a cheaper model. | IT operations |
| Block new work | 100% of budget | Refuse new tasks, let in-flight tasks finish, send waiting work to a human queue. | IT operations, owner informed |
| Security stop | Confirmed loop or suspected compromise | Revoke the agent's credentials, halt it, run cleanup and review. | Security |
Monthly budgets alone are too slow, so add per-task caps on steps, tokens and elapsed time, plus hourly or daily pools. A token budget is not a dollar budget: Google's documented pools are enforced in tokens, with dollars appearing only as a separate estimated-cost metric, while finance thinks in dollars and token prices vary by model. Expect overshoot too: the same documentation warns that concurrent requests admitted before a pool is exhausted can exceed the limit, so set limits below the number you truly cannot cross.
A gateway enforces per request. In strict mode, Google's documented behavior is to reject the call with an HTTP 429 once a pool is exhausted, and a gateway has no way of knowing that call was step four of seven. A half-finished task can cost far more than the tokens saved. Protect these cases:
The pattern has four parts. Check budget when a task starts, so work is refused before it begins. Hold back a completion reserve so admitted tasks can finish. Build agents to treat a rejection as a handled state, with retry limits and a human queue. And give critical workflows a pre-approved emergency allowance that is named, capped, logged and reviewed, never an unlimited exemption.
Routing sends each task type to the cheapest model that meets its quality bar: simple classification and extraction to smaller models, planning and exceptions to stronger ones. Prove quality with evaluations before downgrading, because a cheaper model that retries or escalates more often can raise cost per completed task. Have security approve the routing table too, since a new model or provider can change where your data goes.
Unexplained consumption has a short list of causes: a bug, a changed upstream API, a poisoned prompt, or a stolen credential. All four can look the same on a cost dashboard. Watch for repeated identical tool calls, tokens per task far above baseline, activity at odd hours, and calls to tools or models the agent has never used.
Send those anomalies to your security team as well as your finance contact. Your agent observability traces show what the agent did and why, and your security operations process decides whether it was an accident.
Split the work by decision: IT operates the controls and finance sets the targets.
| Role | Owns |
|---|---|
| Finance | Budgets, unit cost targets, chargeback or showback, token-to-dollar conversion |
| IT | Tagging, gateway policy, thresholds, routing, enforcement |
| Security | Anomaly triage, credential revocation, routing approval |
| Business owner | Each agent's outcome, budget request and exceptions |
The named owner matters most. ServiceNow's release cites LTM, which it says has deployed 1,500 agents, each with an assigned employee ID and manager. No agent should run without one accountable person.
Attribute every call, measure cost per completed task, enforce budgets in stages, protect in-flight transactions, and treat spend anomalies as security events. Tagging, logs and alerts can start now, while vendor features roll out.
By day 30 you should have an owner for every agent, a known unattributed percentage, unit costs for your biggest workloads, and one tested enforcement path. Our AI consulting team can run this plan with you, our custom AI agent builds can include these controls from the start, and steady high-volume workloads are worth comparing against hosted AI options.
AI agent cost governance is the practice of attributing AI spend to each agent, workflow and owner, measuring cost per completed task, and enforcing budgets at runtime through graduated steps such as alert, throttle and block.
Cloud FinOps mostly manages capacity that people provision and review later. Agent spend is set at runtime by the agent's own reasoning, retries and tool calls, so per-task limits and live enforcement matter more than after-the-fact reporting.
Not mid-transaction. The safer pattern is to refuse new tasks at the limit, let in-flight tasks finish or roll back cleanly, and send queued work to a person. Reserve immediate termination for a confirmed runaway loop or suspected compromise.
Both, with separate jobs. Finance sets budgets and unit cost targets, IT runs the attribution and enforcement, security handles anomalies, and a named business owner answers for each agent.
Infonaligy is based in Dallas–Fort Worth and supports AI cost governance programs across our service locations and nationwide through remote delivery.
We help IT and finance leaders attribute agent spend, set unit cost targets, and put safe, graduated enforcement in place.