Micropayments That Actually Work
Why AI Agents Paying AI Agents on BSV Isn't Science Fiction
The Pitch
HTTP 402 “Payment Required” sat dormant for thirty years. A status code waiting for a future that never showed up. Coinbase recently woke it up with x402, their stablecoin protocol for API payments. But there’s another implementation running quieter, on Bitcoin SV, and it’s already handling real money between AI agents.
John Calhoun’s x402 skills for Claude Code and Codex aren’t some whitepaper, or a roadmap. It’s a live system where AI agents discover services, check prices, and pay each other in Bitcoin (BSV) satoshis. All through natural language. No accounts. No subscriptions. No human babysitting the transaction.
This is what machine-to-machine commerce looks like when you stop talking about it and actually build it.
The Protocol: Two Visions of x402
Coinbase’s version is corporate infrastructure. USDC on Base, Polygon, Arbitrum, Solana. A facilitator service handles verification and settlement. Coinbase hosts it. You get 1,000 transactions free each month, then pay $0.001 per transaction after. It works. But it needs Coinbase’s permission, Coinbase’s servers, Coinbase’s fee structure. Or, Stripe with extra steps.
BSV’s version plays by different rules. No facilitator. No accounts. The server checks the transaction itself against the BSV network. The payment *is* the authorization. Stateless. Peer-to-peer. No middleman taking a cut or demanding your email address.
The technical foundation holds up. BRC-120 is the formal BSV standard referencing the frozen x402 v1.0 spec. BRC-121 is a lighter profile for single round-trip payments. Both use BEEF-encoded transactions, BRC-29 payment remittance, and deterministic request binding. Server sends a 402 with price and identity key. Client replies with a signed transaction. One round-trip. Settlement-gated execution. Done.
The Skills: What Actually Works
Calhoun’s x402 skills connect to a live agent registry at x402agency.com/.well-known/agents. Here’s what’s live right now:
Banana Agent — AI image generation (Google Nano Banana Pro). Cost: ~$0.19 per image
Veo Agent — AI video generation with audio (Google Veo 3.1 Fast). Cost: ~$0.75-$1.50 per clip
Whisper Agent — Speech-to-text transcription. Cost: ~$0.0006 per minute
X Research Agent — Twitter/X search, profiles, threads, trending. Cost: ~$0.005-$0.06 per request
1Sat Agent — 1Sat Ordinals inscriptions (any file type). Cost: 200-256,000 sats
NanoStore — File hosting with UHRP content addressing. Cost: ~$0.0004 per MB per year
The flow is dead simple. Type “/x402 generate a photo of a cat in a top hat”. The skill finds the Banana Agent, reads its manifest, runs the BRC-31 authentication handshake (cached for an hour), pays the ~9,000 sats, and hands back the image URL. Fully automatic. No confirmation prompts for typical micropayments.
This isn’t theoretical. These are real services with real pricing, moving real satoshis.
Why BSV Specifically?
The economics matter. BSV transaction fees sit low enough to make per-request payments practical. We’re talking fractions of a cent. On Ethereum or even Base, the gas cost alone would eat a $0.19 image generation alive. On BSV, the protocol fee is noise compared to the service cost.
This is the micropayments promise that Bitcoin’s original design aimed for. Not digital gold. Not a store of value sitting in a vault. A peer-to-peer electronic cash system where machines transact autonomously without asking permission.
The Broader Implications
We’re heading toward a world where AI agents need to pay for services without human intermediation. The current model (API keys, credit cards, OAuth flows) assumes a human setting up accounts, managing billing, handling disputes. Fine for human developers. A bottleneck for autonomous agents.
x402 on BSV cuts through that. An agent discovers a service, pays for it, receives the result, moves on. No account creation. No subscription management. No chargeback risk. The transaction itself is the authorization.
Where this gets interesting:
AI agent marketplaces — agents hiring other agents for specialized tasks
Pay-per-use APIs — no more monthly subscriptions for services you touch twice
Content monetization — articles, media, data feeds priced per access
Decentralized compute — paying for inference, storage, bandwidth on demand
The Caveats
It’s early. The x402 agency registry is small. Six services, all BSV-specific. The MetaNet Client dependency puts you inside the BSV ecosystem, which carries its own tooling and learning curve. And while the protocol itself is stateless, the services still run on traditional infrastructure underneath.
Yeah, Coinbase’s version holds the network effects advantage. USDC liquidity, EVM compatibility, corporate backing, familiar developer workflows. BSV’s version holds the structural advantage. Actually stateless. Economically viable for true micropayments. No facilitator gatekeeping the transaction flow.
These aren’t competitors in the traditional sense. They’re different bets on what machine-to-machine commerce should become. Facilitated and familiar versus permissionless and peer-to-peer.
The Takeaway
After all these decades, HTTP 402 is finally doing the job it was designed for. The Coinbase implementation will likely see broader adoption in the near term. It’s familiar, backed by a major exchange, fits existing workflows.
But the BSV implementation is the one that actually delivers on the original promise. Stateless. Accountless. Machine-verifiable payments at internet scale. Calhoun’s skills prove it isn’t just possible, it’s running today; with real services and real costs.
The future of AI commerce might not look like a subscription dashboard. It might look more like a satoshi-denominated transaction header, verified in milliseconds, with no human ever touching a credit card. That’s probably a relief.