FinOps for AI Agents: Who Spent All the Tokens? — Tisha Chawla & Susheem Koul, Microsoft
Run-level policies cut benchmarked agent spend while completing more runs, suggesting builders should steer loops, context, and tool output before enforcing hard caps.
Microsoft’s TokenOps prototype governs whole agent runs rather than isolated model requests. Across Browser Use and MetaGPT benchmarks, its full policy suite cut **average spend by almost 78%** and raised completion from **67% to roughly 96%** versus simple throttling.
Instrument boundaries between agents and tools, attribute costs per run, and enforce cumulative budgets in the call path. Prefer steering actions such as context compaction and tool-output reduction before halting a run.
Microsoft’s TokenOps prototype governs whole agent runs rather than isolated model requests. Across Browser Use and MetaGPT benchmarks, its full policy suite cut **average spend by almost 78%** and raised completion from **67% to roughly 96%** versus simple throttling. Instrument boundaries between agents and tools, attribute costs per run, and enforce cumulative budgets in the call path. Prefer steering actions such as context compaction and tool-output reduction before halting a run. The figures come from two open-source repositories and unspecified mixtures of stress, simple, and hard scenarios. The proposed self-learning policy module is an intended future state, not a demonstrated capability.
This moves observability and control from individual calls to the economics of an entire agent run, adding cumulative cost as a reliability constraint. The reported benchmark suggests that steering context and tool output can improve both spend and completion relative to simple throttling, but the limited scenario disclosure keeps the result provisional and does not establish a self-learning governor.