Pro - $29 per agent per month.
Built for agents that have real users and real volume. Full API, webhooks, exports, and the Verified Agent badge. Save 2 months on annual billing.
Pro is the right plan for an agent with real outflow volume. The math: a Pro agent doing $500/month in outflow pays $29 subscription + $20 outflow fee = $49 total. The same agent on Free would pay $50 in outflow fees alone, with no API write access, no webhooks, no Verified badge, and a $50 hard cap on total spend authorization. Annual billing drops the equivalent to ~$24/month, making Pro the right choice down to ~$400/month outflow.
Everything on Free, plus the engine room.
- Everything on Free
- Full API access including payment-requests POST
- Signed webhook events (HMAC-SHA256)
- Verified Agent badge (after GitHub verification)
- Custom branding on the public page
- Domain verification (DNS TXT)
- Per-agent spend policies (set/edit via API)
- Data exports (CSV and JSON)
- No daily volume cap
- Standard API rate limits (10x Free)
- Email support, typical response within 24 hours
The most-used plan on Blockchain0x.
- Solo developers running a single revenue-generating agent
- MCP server operators serving paid clients
- Builders who want their agent to look professional and verified
- Anyone whose agent outflow crosses ~$483/month per agent (the Free -> Pro break-even)
When the numbers say upgrade.
The crossover point on pure outflow-fee math is $483/month per agent in outflow volume. Below that, Free's 10% outflow fee is cheaper than Pro's $29 subscription plus 4% outflow fee. Above, Pro is. Here is the derivation.
The break-even equation
Free cost = 0.10 x V (outflow)
Pro cost = 29 + (0.04 x V) (outflow)
Solve for V where Free cost = Pro cost:
0.10 x V = 29 + (0.04 x V)
0.06 x V = 29
V = 483.33
Annual billing on Pro: 29 -> ~24/month equivalent
0.10 x V = 24 + (0.04 x V)
0.06 x V = 24
V = 400Below V = $483/month outflow: Free is cheaper. Above: Pro is. At exactly $483: identical cost (~$48 either way).
Worked examples at common volumes
| Monthly outflow | Free total (10%) | Pro total ($29 + 4%) | Savings on Pro |
|---|---|---|---|
| $100 | $10 | $33 | -$23 (Free wins) |
| $300 | $30 | $41 | -$11 (Free wins) |
| $483 | $48 | $48 | $0 (break-even) |
| $750 | $75 | $59 | +$16 (Pro wins) |
| $1,000 | $100 | $69 | +$31 |
| $2,000 | $200 | $109 | +$91 |
| $5,000 | $500 | $229 | +$271 |
Reasons to upgrade earlier than $300/month
- API write access matters more than the subscription cost. Free has read-only API. Pro lets your agent code call POST /v1/payment-requests, which is the difference between a passive tip jar and an autonomous earning agent.
- Webhooks turn on real-time UX. On Free you can only poll for a transaction after the fact to find out a payment landed. On Pro, a signed payment.received event POSTs to your callback within seconds. For agent-driven workflows where the next action depends on the payment, this is the entire game.
- The Verified Agent badge lifts conversion 20-40%. On shared agent links, the badge is what separates "pay this random URL" from "pay this real business". The conversion lift typically covers the subscription within a handful of extra payments.
- The $50 Spend Permission cap on Free gets in the way. Free caps total spend authorization at $50 per agent and outflow at $100/agent/day. Pro raises the Spend Permission cap to $10,000 and removes the daily outflow cap entirely.
What Pro actually looks like in practice.
Concrete monthly numbers from three customer shapes we see most often. Names are illustrative.
"sql-helper" - solo developer
A SQL-from-natural-language agent that charges $0.10 per query. Runs 200 paid queries/day at $20/day = $600/month inflow, with $500/month outflow on tool calls. Bill: $29 subscription + $20 outflow fee = $49/month. Margin: $551 before infra costs, comfortably above the Free-tier total of $50.
- - Webhook on every paid query to release the SQL output
- - GitHub Verified badge (their repo has 800 stars)
- - Custom hex color on the public page matching their brand
"docs-mcp" - MCP server operator
A paid MCP server that exposes documentation-search tools to Claude/Cursor clients. Charges $0.02 per query. Runs 80,000 paid queries/month = $1,600 inflow, of which $1,200 is paid back out to upstream search infra. Bill: $29 subscription + $48 outflow fee = $77/month. Same agent on Free would have paid $120 in outflow fees alone, plus would have been blocked entirely by the $100/agent/day outflow cap.
- - x402-compatible payment flow for AI clients
- - Domain Verified badge (proves the MCP server is theirs)
- - CSV exports of usage for monthly reporting to their team
"market-report-bot" - paid research agent
A research agent that produces $25 LLM-benchmark reports on demand. Runs 20 reports/month = $500 inflow, with the operator withdrawing the proceeds monthly = $500/month outflow - right at the Free-vs-Pro break-even ($50 either way). They upgraded for the badge, not the math. The Verified badge raised commission-acceptance rate from 8% to 13% within two weeks of going live.
- - Verified Agent badge on the public page
- - Programmatic payment requests (no manual hosted-URL hand-off)
- - Webhook to start report generation the moment payment confirms
The Verified Agent badge, in detail.
GitHub verification is a one-click OAuth step that ties the agent to a real developer identity. Pro includes it; it does three concrete things on the public agent page and in your analytics.
1. The Verified Agent badge on the public page
A visually distinct check-mark badge appears next to the agent name in the hero of the public page. Hovering reveals "GitHub verified: github.com/your-handle, confirmed on YYYY-MM-DD". The badge is also emitted in the page's JSON-LD as a schema.org/Certification entity, which AI search engines like Perplexity and ChatGPT use to differentiate verified agents in citations.
2. Higher conversion on shared links
When someone shares your agent's URL on X, LinkedIn, or in a GitHub README, the rendered OG image includes the Verified badge inline with the agent name. Click-through-to-pay rates on verified-badge pages are consistently 20-40% higher than on unverified equivalents (our internal measurement across launched customers). The badge is what makes a buyer believe the agent is run by a real person they can find on the open internet.
3. Linked GitHub profile under your agent name
Your verified GitHub username renders as a clickable link on the agent page (github.com/your-handle). Visitors can verify the developer identity for themselves: see your repos, your contributions graph, your account age. This is the strongest non-financial trust signal you can earn at the Pro level. Domain verification (also included on Pro) layers on top for an even stronger signal when you have a custom domain to use.
We re-check the GitHub account status monthly. If the account is deleted or made private, the badge is automatically revoked and you get a notification email. You can revoke the OAuth grant at any time from your GitHub settings; the snapshot remains valid but the connection cannot refresh.
Move to Business when one of these is true.
Pro is the right plan for the overwhelming majority of agent operators. Business exists for a narrower shape: high volume, team operators, or strict audit requirements. If the math justifies it, the upgrade is one click.
- You need full audit logs for compliance
- You need a higher Spend Permission cap ($100k vs $10k)
- You run a team of operators sharing agents
- You want higher API rate limits
The strict cost-based crossover from Pro to Business is $1,000/month per agent in outflow volume. Below that, Pro is cheaper. Above, the lower 2% outflow fee on Business pays for the $20/month subscription difference vs Pro. Many users upgrade for the audit log or the higher Spend Permission cap before the math says to.
See the Business plan