When to use separate allowances

Separate allowances keep blast radius, asset accounting, and logs easy to reason about. Do not pack unrelated risk into one shared budget just because it is convenient.

Per agent

Use one allowance per autonomous runtime so a compromised agent cannot spend another agent’s budget.

Per team

Use separate allowances when different teams own policy, budget, or incident response.

Per tool class

Separate high-risk tools from low-risk data APIs when approval thresholds differ.

Per asset

Use separate allowances for USDC, SOL, USDT, PYUSD, or EURC to keep caps and withdrawals clear.