Agent spend alerts that don't cry wolf: choosing thresholds
GetAgentCap team · published 10/19/2026
An alert that fires every day gets muted, and a muted alert is worse than none. Good thresholds for agent spend come from the agent's own history and a small number of rules you can explain in one sentence each.
Start from the budget, not from fear
The simplest useful alert is a percentage of the budget: warn at 50 percent, act at 80, treat 100 as an incident. These lines are easy to reason about because everyone knows what the budget is.
Pick the budget period to match how the agent actually runs. A daily budget for a job that spends weekly in bursts will alert constantly; a monthly one for a runaway loop will alert far too late.
Add one rate-based rule
Budget percentages miss speed. An agent that spends a day's budget in ten minutes is in trouble even at 20 percent of the month. A single rule such as spend in the last hour exceeding some multiple of the usual hourly average catches loops without a pile of special cases.
Set the multiple from a week or two of real data, then adjust. A rule you tuned against history will rarely fire on normal days.
Make each alert say what to do
An alert should name the agent, the amount, the period and the next step: check the agent's recent payments, pause its job, or raise the budget on purpose. If the right action is always the same, the alert is a candidate for automation on the signing side.
Review fired alerts weekly. Ones nobody acted on get a higher threshold or get removed; ones that arrived late get a lower one.