sipi.bot is the pre-spend firewall for autonomous AI agents. One HTTP call checks every proposed payment against your caps, velocity limits, and merchant rules—then returns APPROVED, BLOCKED, or FLAGGED with a deterministic rules check, before money moves.
The one promise of this page: transactions routed through sipi.bot are evaluated against your rules before execution. The calling agent or payment integration must honor the decision. Hope is not a spending policy.
Teams running autonomous agents with paid APIs, cloud provisioning, ad spend, data purchases, or payment rails.
The observable risk: retry loops, unapproved merchants, and distributed agent budgets that no single dashboard catches before the charge clears.
✨ Try it right now — no signup, no key. Copy, paste, run.
curl -X POST https://sipi.bot/v1/transactions/evaluate \sipi.bot is the spend layer for the same agent protocols that move money autonomously. We plug in before the transaction, not after the incident.
That's what happens the moment you deploy an autonomous agent. Here's the difference one API call makes.
Your agent asks permission first. It's HTTP, so any agent can call it — and an MCP tool, so Claude Code / Cursor / Hermes call it natively.
Not a suggestion. Not a soft preference. A deterministic firewall. We call it The 3-Decision Spend Firewall™. Your agent calls it before every spend, it answers in under 5 ms, and the answer is final.
APPROVED • BLOCKED • FLAGGED. Three answers. Five milliseconds. Every transaction. That is the firewall.
APPROVED and your agent proceeds — logged for the audit trail.BLOCKED and no money moves.FLAGGED and routes it to your human-in-the-loop approval queue.| Approach | Stops runaway spend | Latency | Audit log | Cost |
|---|---|---|---|---|
| Trust the prompt | ❌ No | — | ❌ No | $0 (until it isn't) |
| Provider spend cap | ⚠️ Per-provider only | — | ⚠️ Partial | Varies |
| Manual review | ✅ Yes | Minutes+ | ⚠️ Separate notes | Variable |
| sipi.bot | ✅ Yes | No model call | ✅ Queryable | $99/mo |
Every transaction an agent attempts is checked against these before any money moves. Turn on the ones that matter for your workload.
unknown-gpu.ru is blocked unless you've allowlisted it.Any time an autonomous agent holds a payment method, it needs a spending policy it can't override. Common deployments:
Agents that buy compute, API credits, ads, or SaaS on their own. sipi.bot enforces the budget the prompt can't be trusted to hold.
Swarms where dozens of agents spend in parallel. A shared daily cap and velocity limit stop the fleet from compounding one mistake. See CrewAI and LangChain.
Agents transacting over machine-payment rails. sipi.bot is the approval layer in front of the wallet — see the x402 approach.
Background agents that provision infrastructure or pull paid data. The queryable audit log shows exactly what was bought and why.
Because the name gets misread: sipi.bot is a payment-control spend firewall for autonomous AI agents. It is not a SIP/VoIP telephony bot, and it is not an AI-bot-blocking tool or web-application firewall (WAF). It never holds your money — it's a decision API that returns approve, block, or flag with a deterministic rules check, and your existing payment rail is what actually moves (or doesn't move) the funds.
Not $0.05 per call. A flat firewall you never think about.
Same price whether your agent makes 10 or 10,000 decisions. No per-call fees. No overage tier.
🛡️ Guarantee: green-light a rule violation, month is free
Free self-host core • open on GitHub
One email a day for five days. Day 1: how retry loops create runaway spend. Day 2: the six rules that stop it. Day 3: wiring the decision into your agent. Day 4: the eval suite. Day 5: the deployment checklist. No sales pressure - unsubscribe anytime.
Joining the list does not sign you up for anything paid. The hosted plan is a separate checkout.
TL;DR: sipi.bot is a spend firewall for autonomous AI agents. Your agent asks permission before it spends; sipi.bot returns approve, block, or flag with a deterministic rules check based on your rules — over HTTP, MCP, or CLI, for a flat $99/month.
A spend firewall sits in front of every transaction an autonomous AI agent attempts and evaluates it against your rules — approving, blocking, or flagging it before any money moves. sipi.bot returns a decision with a deterministic rules check over HTTP, MCP, or CLI.
Your agent calls sipi.bot before it spends. sipi.bot checks the transaction against per-transaction, daily, velocity, merchant, category, and time rules and returns approve, block, or flag. Velocity limits kill runaway retry loops instantly, and unknown merchants are blocked unless allowlisted.
Hosted plans are flat-rate: Team is $99/month and Business is $499/month, both with unlimited transaction evaluations — no per-call fees, no metering, no overage tiers. The open-source core is MIT-licensed and free to self-host forever, and the full plan comparison is on the pricing page.
Yes. sipi.bot is a native MCP tool, so Claude Code, Cursor, and Hermes call it directly, and it also exposes a plain HTTP API and a CLI so any agent runtime can use it. Client wrappers for LangChain, CrewAI, the OpenAI Agents SDK, and the Vercel AI SDK take a few lines each.
If sipi.bot green-lights a spend that breaks one of your active rules, that month's subscription is free. Every decision is written to a queryable audit log recording the rule that fired, the amount, and the reason, so you can review exactly why anything was approved, blocked, or flagged.
Yes. sipi.bot sits in front of agentic-payment rails including x402, Google's AP2, and Coinbase AgentKit as the approval layer — your agent asks sipi.bot for a decision before it settles a payment on any of them. It's rail-agnostic because it evaluates the transaction (amount, merchant, category), not the plumbing.
No. sipi.bot is a decision API, not a wallet or a processor. It returns approve, block, or flag; your existing payment rail is what actually moves the funds. That means there's no float, no custody, and nothing new to reconcile — you're only adding a control check in front of what you already use.
Yes. The core is MIT-licensed and open on GitHub, free to self-host forever. The hosted plans add the live dashboard, managed approval queue, and timestamped audit log storage. See the self-hosted guide.
A provider cap (OpenAI, Anthropic, a cloud bill) only limits spend on that provider, and usually only tells you after the fact. sipi.bot sits in front of every transaction across every merchant, decides in real time before money moves, and keeps one audit log for all of it — see how it compares to Stripe Radar.
No vanity metrics, no inflated claims, no fabricated testimonials. These are facts you can verify yourself.
A deterministic rules engine — no model in the decision path. How sipi.bot handles security →
No paying customers yet — these are shipped, verifiable fixes, not client logos. Pricing & pilot →