Spend Control for Composio
Composio gives agents access to hundreds of tools and apps. More tools, more spend surfaces — the guard keeps the money path honest.
Why Composio agents overspend
300+ connected tools mean 300+ potential paid calls.
Tool access is permissive by design.
No dollar-level budget at the tool layer.
How it works
Compose the sipi.bot guard into your tool set: before any spend-capable tool runs, the agent gets a deterministic decision.
Rules that fit
Merchant allowlist for paid tools.
Per-agent daily ceiling.
Category rule: data vs compute vs payments.
Guard in the tool set
const res = await fetch("https://sipi.bot/v1/transactions/evaluate", {
method: "POST", headers: { "Content-Type": "application/json" },
body: JSON.stringify({ amount: 15, merchant: "connected-app.com", category: "api" }),
});
const { decision } = await res.json();Every connected tool, one gate.
FAQ
Does this slow tool calls?
No — ~5 ms per check, spend-capable tools only.
Can I whitelist per integration?
Yes — the merchant allowlist maps to connected apps.
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