Integration

sipi.bot + CrewAI Integration — Agent Spend Firewall

CrewAI multi-agent systems need per-agent spend controls. sipi.bot provides isolated workspace policies for each connected API key.

· Published 2026-07-19

Integration

CrewAI multi-agent systems need per-agent spend controls. sipi.bot provides isolated workspace policies for each connected API key.

Getting Started

Add the sipi.bot evaluation call before any paid tool execution in your CrewAI agent. The API returns APPROVED, BLOCKED, or FLAGGED without a model call. Full documentation and code examples are available in the sipi.bot GitHub repository.

Get started — $99/mo Framework integrations

Detailed integration walkthrough for CrewAI Integration — Agent Spend Firewall

Integrating sipi.bot with CrewAI Integration — Agent Spend Firewall adds a policy enforcement layer between your agent's intent to spend and the actual transaction. The integration is deliberately minimal — a single API call with four fields (agent ID, merchant, amount, intent) — but the effect is comprehensive: every transaction must pass the policy check before money moves.

Step-by-step setup

  1. Install the sipi.bot SDK or use the HTTP API. If CrewAI Integration — Agent Spend Firewall runs on Python, run pip install sipi-bot. For other runtimes, use the REST API at POST https://sipi.bot/v1/transactions/evaluate. Authentication is via bearer token.
  2. Identify the spend paths. Search your CrewAI Integration — Agent Spend Firewall agent code for every place it can initiate a payment, charge, API call, provisioning action, or purchase. Each one needs a policy check inserted before the actual transaction executes.
  3. Wrap each path with a policy check. The check takes four parameters: agent ID (string), merchant (string — the vendor or destination), amount (float in USD), intent (string — free-text description of what the transaction is for). Example: sipi.check(agent_id="agent-1", merchant="openai", amount=0.50, intent="LLM call")
  4. Handle the response. sipi.bot returns a JSON object: {"decision": "APPROVED"|"BLOCKED"|"FLAGGED", "reason": "...", "transaction_id": "...", "policy_version": "..."}. Your agent must handle all three outcomes. Do not assume APPROVED is the only response.
  5. Test each path. Run one test for each outcome: a small approved transaction, a blocked transaction (exceed a limit), and a flagged transaction (exceed the approval threshold). Verify the audit log captures all three with correct details.

Testing your integration

After setup, run the integration with sipi.bot's sandbox mode first (set header X-Sipi-Mode: sandbox). Sandbox mode evaluates policies and writes to the audit log but never blocks a real transaction. Use it to verify your integration and tune your limits for 24 hours before enabling enforcement. Most teams find this catches 2-3 configuration issues that would have caused false positives in production.

Pricing

sipi.bot starts at $99/month for unlimited transaction evaluations. No per-call fees, no tier upgrades for higher volume. The integration with CrewAI Integration — Agent Spend Firewall is supported out of the box, and setup typically takes under an hour for teams familiar with their agent's codebase.