Skip to main content
Budgets are spending limits enforced at the agent level. Saturn supports two cap types: Caps are independent of credit balance. An agent with 100increditsbuta100 in credits but a 5/day cap cannot spend more than $5/day.

Why Caps Exist

Credits answer: “How much money is available?” Caps answer: “How much should this agent be allowed to spend?” Without caps:
  • A bug can drain your entire credit balance in seconds
  • No economic boundaries between workloads
  • Cost attribution becomes cost allocation after the fact
Caps create runtime enforcement. The call is rejected before it happens.

Enforcement Order

When Saturn receives a request:
  1. Is the agent active? (not killed)
  2. Is the capability allowed?
  3. Does quoted cost exceed maxPerCallUsdCents? → Reject
  4. Does (today’s spend + quoted cost) exceed maxPerDayUsdCents? → Reject
  5. Does quoted cost exceed available credits? → Reject
  6. All checks pass → Execute

Setting Caps

Handling Budget Errors

Cap Recommendations

Start with tight caps. You can always increase them. You can’t un-spend money.

Common Mistakes

Example: Protecting Against Infinite Loops

Without Saturn:
With Saturn: