A token budget caps how much a specific API token may spend, with daily, weekly, or monthly windows and a warning threshold. A hard limit blocks requests when reached; a soft limit only flags the token. Budgets stop a single runaway integration from spending the whole workspace balance.
Why it matters
A single runaway integration can drain a shared workspace balance. Budgets put a ceiling on one token without affecting the others.
How it works
Each token gets a spend limit with a daily, weekly, or monthly window and a warning threshold. A hard limit blocks requests at the cap; a soft limit only flags the token. Changing the period starts a new window immediately.