sipi.bot — the spend firewall for autonomous AI agents
You gave an autonomous agent your credit card and no spending limit. sipi.bot is the firewall that approves, blocks, or flags every transaction against your rules — before a single dollar moves.
One capability, three surfaces:
- MCP tool — Claude Code / Cursor / Hermes call
evaluate_spendnatively. - HTTP API — any agent
POST /v1/transactions/evaluate. - CLI — verify without an agent.
10-second test
pip install sipi-bot
sipi-bot eval --amount 6200 --merchant unknown-gpu.ru --category compute
# -> {"decision": "BLOCKED", "reason": "Transaction $6,200.00 exceeds per-transaction limit $500.00."}
sipi-bot serve --port 8080 # landing + dashboard + API
Or from source:
python3.11 -m spendfirewall.cli eval --amount 6200 --merchant unknown-gpu.ru --category compute
Then open http://localhost:8080 (landing), http://localhost:8080/dashboard (control room), http://localhost:8080/pricing (Team $99 / Business $499).
Hosted: sipi.bot · dashboard · get an API key →
The core call an agent makes before spending
curl -X POST https://sipi.bot/v1/transactions/evaluate \
-H "Authorization: Bearer sk_live_..." \
-d '{"amount": 6200, "merchant": "unknown-gpu.ru", "category": "compute"}'
Returns one of: APPROVED (go), BLOCKED (do not spend), FLAGGED (human must approve).
Rule types
per_transaction, daily_total, velocity (runaway protection), merchant_block,
merchant_allow (allowlist), category_limit, time_window, approval_threshold.
First BLOCKED wins. FLAGGED is non-blocking (queued for human approval).
Eval gym (the guarantee + the sales asset)
python3.11 -m spendfirewall.eval.run_eval # 53 scenarios -> eval_report.json + .md
53/53 passing. Served live at /eval. This is what backs the guarantee:
if the firewall green-lights a spend that breaks your rule, that month is free.
MCP config
{ "mcpServers": { "sipi-bot": { "command": "python", "args": ["-m", "spendfirewall.mcp_server"] } } }
Framework integrations
Drop-in "spend guardrails" recipes — each verified live against https://sipi.bot:
- LangChain & CrewAI —
@tool/BaseToolwrappers + zero-depsipi_guard.pyclient - OpenAI Agents SDK —
@function_toolguard - Vercel AI SDK —
tool({execute})guard +sipiGuard.tsclient
The core call is always the same: evaluate(amount, merchant, category) → APPROVED / BLOCKED / FLAGGED.
Deploy (Fly.io)
flyctl launch --no-deploy --copy-config --name sipi-bot-firewall
flyctl volumes create sf_data --size 1 --region iad --yes
flyctl deploy
flyctl certs add sipi.bot
Stdlib-only (http.server, sqlite3). No framework, trivial deploy. pip install mcp only for the MCP surface.
Metadata
Release files for sipi-bot 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| sipi_bot-0.1.0.tar.gz | 39.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sipi_bot-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 83.9 kB
Release files / sipi_bot-0.1.0.tar.gz
| Download URL | sipi_bot-0.1.0.tar.gz |
|---|---|
| Size | 39.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
efb7edc080b3ef8470c834052aa308b60517828f6bacb1d484513fc6ee46690f
|
|
BLAKE2b-256 checksum How to use checksums |
059d5410cb651f2791027f6a9501da49ab72666c0ecf138df906d0c9e0724a23
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 18, 2026.
Transparency logRelease files / sipi_bot-0.1.0-py3-none-any.whl
| Download URL | sipi_bot-0.1.0-py3-none-any.whl |
|---|---|
| Size | 44.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6d76fd9563b9a1755377202ad1ed8ed1d05e83d9cf22f97c5585decc017da1d2
|
|
BLAKE2b-256 checksum How to use checksums |
abf0a40c36a0985eab028170692bbbcaeba8e3d1ce5ea6b9a9d6d93c0ad8966e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 18, 2026.
Transparency logSecurity for sipi-bot 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for sipi_bot-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.