Spend Control for ElizaOS
ElizaOS powers autonomous agents in the crypto economy — trading, tipping, and transacting onchain. Speed is the point; a gate is the requirement.
Why ElizaOS agents need a gate
Autonomous agents transact onchain where settlement is fast and irreversible.
A retry loop on a payment rail is damage at settlement speed.
No native budget enforcement in the agent runtime.
How it works
Call sipi.bot before any transaction: amount, merchant, category → APPROVED, BLOCKED, or FLAGGED in ~5 ms, fully logged.
Rules that fit ElizaOS workloads
Per-transaction cap for onchain payments.
Merchant allowlist for known counterparties.
Velocity limit so loops die before settlement.
Guard call
const res = await fetch("https://sipi.bot/v1/transactions/evaluate", {
method: "POST", headers: { "Content-Type": "application/json" },
body: JSON.stringify({ amount: 0.5, currency: "ETH", merchant: "counterparty.eth", category: "transfer" }),
});
const { decision } = await res.json();The rail settles; sipi.bot decides.
FAQ
Does sipi.bot hold crypto?
No — it's a decision API. Your wallet and rail still settle.
Is 5 ms fast enough for trading?
The gate is on the payment path, not the market-data path — 5 ms is fine.
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