Per-Transaction Cap Calculator
What cap blocks the catastrophic single call? Enter your max tolerable single-transaction loss and see recommended caps across risk levels.
Tight (20% buffer)
Medium (50% buffer)
Loose (80% buffer)
The per-transaction cap is the single most important rule. Pair with velocity cap (catches loops) and daily total (catches aggregate).
The three caps every agent needs
| Cap | Catches | Without it |
|---|---|---|
| Per-transaction | One catastrophic call | $500 GPU instance, $200 API batch |
| Velocity | Retry cascade | 50x loop overnight |
| Daily total | Aggregate burn | Death by small calls |
Frequently asked questions
Related resources
How do I know my worst-case transaction?
Audit your agent's tool call paths. The worst case is the most expensive single action: provisioning a GPU ($2-10/hr), calling an enterprise API ($1-50/call). Set the cap at 50% of that amount.
Can I have different caps per agent?
Yes. sipi.bot supports per-agent policies keyed to the agent's API key.