Spend Control for AG2
AG2 builds multi-agent systems where agents converse, delegate, and call tools — parallel spend by design. The firewall gives the fleet one budget.
Why AG2 systems overspend
Multi-agent conversations spawn many tool calls per turn.
Parallel agents compound spend during a single task.
No built-in dollar-level budget.
How it works
Add the guard as a tool available to the agents that spend. Decisions are deterministic and shared across the fleet.
Rules that fit AG2 workloads
Shared daily ceiling across the conversation's agents.
Velocity limit per agent.
Category rule for inference vs data vs payments.
Guard tool
from sipi_guard import sipi_guard
# Agents call this before spending:
decision = sipi_guard(amount=80, merchant="api.vendor.com", category="api")
# APPROVED | BLOCKED | FLAGGEDOne fleet, one budget.
FAQ
Does the shared ceiling cover all agents?
Yes — rules scoped to the group share one budget.
What about legitimate parallel work?
Set the ceiling at a level that fits legit fan-out; the cap only bites when the fleet exceeds it.
Related
Stop the next $12,400 night.
One API call (or MCP tool) in front of every agent transaction — APPROVED, BLOCKED, or FLAGGED, deterministic, ~5 ms, fully logged.
See plans — from $99/mo Try a live check