SPEND GOVERNOR: stop the runaway agent before the bill does
Agents rarely blow a monthly budget in one call. They burn it in a retry storm, loop on the same call, or spend in amounts that each look harmless. The governor checks every charge against nested budgets (agent → workflow → tenant), a spend rate at every level and a loop counter, atomically, and trips a breaker the agent cannot reset itself.
#12 of the CAIN-42 Top 25 4 gaps found and fixed today 1.1.0 live since 2026-11-02 15:31Z (verified on both gateway instances)
held on today's blind set, before any change
after the fixes
racing $1 charges allowed against a $10 limit: exactly the limit
ways for the agent to reset its own breaker
Try it
| Budget | Spent / limit | Rate window | State | Runs out in |
|---|
Live since 2026-11-02 15:31Z: the loop with varied name case trips on the 7th call.
On this site
How it works
One transaction per charge.
Spend lab
The interactive tree.
The three breakers
Budget, rate, loop.
Races
Why parallel agents cannot overspend.
Resets
Only a person, only that trip.
Evidence
20 cases, every row.
Verify it yourself
Signed trip ledger.
API
Routes.
Limits
Honestly.
Use cases
Where it fits.
2026-11-02 upgrade
What we broke and fixed.
FAQ
Questions.
FIRME AI CORPORATION · CAIN-42 is a Byzantine trust fabric. Numbers marked "our own check" were run by us, not by an independent party. Nothing on these pages is a certification.