x402 vs Stripe vs no monetization
| Rail | Fee per txn | Net per txn | Monthly net | Annual net |
|---|---|---|---|---|
| x402 (USDC on Base) | $0.01 | $1.99 | $29,850 | $363,175 |
| Stripe (2.9% + $0.30) | $0.36 | $1.64 | $24,630 | $295,560 |
| No monetization | — | $0.00 | $0 | $0 |
x402 keeps $1.99 of every $2.00 request. Stripe keeps $1.64. The gap at this price is $0.35/txn in x402's favor — $5220/mo extra.
Not wiring any payments leaves $29,850/mo ($358,200/yr) on the table.
Here's the math
- Daily paid requests
50,000 × 1% = 500 - Monthly paid requests (30d)
500 × 30 = 15,000 - Monthly gross
15,000 × $2.00 = $30,000 - Protocol fee (0.5%)
$30,000 × 0.5% = $150 - Monthly net
$30,000 − $150 = $29,850 - Annualized net
$29,850 × 12 ≈ $363,175
Wire it up
The x402 middleware is ~20 lines on a Hono/Express/Next route.
It issues a 402 Payment Required with a USDC settlement
challenge; the agent pays; you return the response. I ship this as a
productized engagement: 1 week, $2,500 flat, USDC on Base.
You keep the keys, the code, and every cent of revenue.
Wire x402 on your API in 1 week — $2,500 → Or ask a question first