Business - $49 per agent per month.
For agents at production volume. Audit logs, advanced policies, team access, $100k Spend Permission cap, and the lowest outflow fee we offer. Save 2 months on annual billing.
Business is for agents that move real money or matter to a real team. The 2% outflow fee makes economic sense when monthly outflow crosses roughly $1,000 per agent (~$850 on annual billing). Below that, Pro is the better fit.
Everything on Pro, plus the controls operators ask for.
- Everything on Pro
- 2% outflow fee (lowest available)
- Spend Permission cap up to $100,000 per agent
- Full audit log of every action that touches an agent
- Custom Open Graph images per agent
- Higher API rate limits (10x Pro)
- Agent-level seat sharing (3 team members can manage one agent)
- Priority email support, typical response within 4 hours
- Slack support channel at scale (negotiated separately)
Built for teams running money-moving agents.
- Web3 automation agencies managing many client agents
- Mid-market companies running AI agents in customer-facing roles
- Operators with compliance or audit requirements
- Anyone processing $1k+/month per agent in outflow volume (the Pro -> Business break-even)
Scale without leaving Blockchain0x.
- Extra seats at $5/seat/month for larger teams
- Multiple Business agents in one workspace for parallel client work
When the 2% outflow fee pays for the $20 subscription difference.
The strict crossover from Pro to Business is $1,000/month per agent in outflow volume. Below that, Pro is cheaper. Above, the lower outflow fee on Business pays for the higher subscription. Annual billing pulls the break-even slightly lower (~$850/month outflow). Here is the derivation.
The break-even equation
Pro cost = 29 + (0.04 x V) (V = monthly outflow)
Business cost = 49 + (0.02 x V)
Solve for V where Pro cost = Business cost:
29 + (0.04 x V) = 49 + (0.02 x V)
(0.02 x V) = 20
V = 1000
Annual billing equivalent rates (~$24 Pro, ~$41 Business per month):
24 + (0.04 x V) = 41 + (0.02 x V)
(0.02 x V) = 17
V = 850Below V = $1,000/month outflow per agent: Pro is cheaper. Above: Business is. At exactly $1,000: identical cost ($69 either way on monthly billing).
Worked examples at common volumes
| Monthly outflow | Pro total ($29 + 4%) | Business total ($49 + 2%) | Savings on Business |
|---|---|---|---|
| $500 | $49 | $59 | -$10 (Pro wins) |
| $1,000 | $69 | $69 | $0 (break-even) |
| $2,000 | $109 | $89 | +$20 (Business wins) |
| $5,000 | $229 | $149 | +$80 |
| $10,000 | $429 | $249 | +$180 |
| $25,000 | $1,029 | $549 | +$480 |
| $50,000 | $2,029 | $1,049 | +$980 |
For agents at production scale (think: an MCP server taking thousands of paid invocations daily, an API behind a paywall used by many agents), the math compounds quickly. A single $50k/month agent saves $480/month on Business vs Pro - $5,760/year on one agent, before counting the non-cost features. Below the $2k crossover, Pro remains the right choice unless one of the non-cost triggers applies.
Caps that hold even when the agent is prompt-injected.
A spend permission sets how much an agent can send: a per-transaction cap and a per-period allowance. Both run on every outgoing payment at the API layer, not in the agent's code, so a payment that exceeds either is rejected before it leaves the wallet.
Read it back from the API
You set spend permissions in the dashboard. The API exposes them read-only, so your monitoring can confirm what is in force on each agent.
GET /v1/agents/ag_abc123/spend-permissions
{
"allowance_wei": "100000000", // 100 USDC per period
"per_tx_wei": "10000000", // 10 USDC per transaction
"period_seconds": 86400, // daily (also 604800 / 2592000)
"start_at": "2026-06-01T00:00:00Z",
"end_at": null,
"revoked_at": null
}Operational rules
- Spend permissions are set in the dashboard. The API exposes them read-only (GET /v1/agents/:agentId/spend-permissions); the POST/DELETE routes are intentionally blocked.
- Both checks run on every outgoing payment: the per-transaction cap (per_tx_wei) and the per-period allowance (allowance_wei) over the period_seconds window. A payment that exceeds either is rejected.
- Editing a permission applies immediately to subsequent payments. Payments already broadcast on-chain are not reversible.
- Spend permissions govern outgoing payments only. Anyone can pay your agent at any time regardless of the permission.
- To stop an agent spending entirely, set the allowance and per-transaction cap to zero. The agent cannot send USDC regardless of what its code or prompt says.
Every action that touches an agent, attributed.
The Business plan records every action that touches an agent, with full attribution: who did it, when, and the before/after of the change. Export it to JSON or CSV from the dashboard for any client or auditor review.
What lands on every entry
| Field | Type | Description |
|---|---|---|
| Timestamp | time | When the action happened, in UTC. |
| Agent | reference | Which agent the action affected. |
| Actor | reference | The human, API key, or system that took the action. |
| Action | category | What happened: a payment, a settings change, a seat change, a key rotation. |
| Outcome | status | Whether the action succeeded or was rejected. |
| Before / after | snapshot | The state on either side of a change. |
Export and integration
- Dashboard export: filter by date range, action, actor, and agent. Download as JSON or CSV.
- Per-agent scoping: export a single agent's log so one client's records never expose another's.
- Attribution: every entry names who took the action and shows the before/after of the change.
Two kinds of seats, one workspace.
Business introduces a seat model designed for agencies and teams that operate many agents with different operators per agent. Two seat types, with different scopes and prices.
3 included per Business agent
A person who can see and manage ONE specific agent: edit settings, view transaction history, set spend permissions, view that agent's audit log. They cannot see other agents in the workspace, cannot change billing, cannot add or remove team members.
Use case: client operators for an agency. Operator A works on Client X's agent only; Operator B works on Client Y's agent only; neither sees the other.
1 included, $5/seat/month for more
A person with full workspace visibility: every agent, billing, team management, plan changes. The workspace owner is the first workspace seat by default. Add more for senior operators or for finance/ops people who need cross-workspace visibility.
Use case: agency owner, ops lead, finance person who reconciles invoices, security/compliance reviewer.
Adding and removing seats
- Workspace owner invites by email from the dashboard. Invitee accepts via email link; account is created (or linked to existing) on first sign-in.
- Removing a seat is immediate; the removed person's API keys are revoked atomically with the removal.
- Every seat add, role change, and removal is recorded in the audit log with full attribution.
- Two-factor authentication is required for workspace seats; agent-level seats can opt in.
Four Business-plan questions worth answering.
Is Business worth it before my agent crosses $1,000/month in outflow volume?
How are team seats different from workspace seats?
Can I export the audit log for compliance review?
Do I get a discount if I run 10+ Business agents?
Run agents at production volume.
Upgrade any agent to Business from the dashboard, or talk to the founder.