An onchain agent now hits 0x's Swap API the way a vending machine takes a coin: it drops $0.01 in USDC from its own wallet and gets a swap quote back. No API key, no account, no monthly bill. 0x Protocol [opened its Swap API to AI agents](https://thedefiant.io/news/defi/0x-swap-api-ai-agents-usdc-payment-x402) over the x402 standard, built on Alchemy's AgentPay — and the part worth your attention isn't the price. It's that the agent paid for itself, with no human in the billing loop.
How a penny moves
The mechanism is the HTTP 402 "Payment Required" status code finally doing the job it was reserved for back in the early web. The flow is short:
- ▸An agent sends a request to the 0x Swap API endpoint.
- ▸The server answers
402 Payment Requiredinstead of returning data. - ▸The agent signs a $0.01 USDC payment onchain from its own wallet.
- ▸A proxy verifies the transaction, then releases the quote — or executes the swap.
Payment settles via x402 on Base and Solana, or through the Machine Payment Protocol (MPP). Behind that endpoint sits 0x's aggregation across more than nine chains, over 130 liquidity sources, and more than 9 million tokens, [according to Crypto Briefing](https://cryptobriefing.com/0x-swap-api-ai-agents-usdc/). The agent doesn't need to know any of that. It needs a wallet with a balance.
"No API key" is the whole story
The API-key model quietly assumes a human. Someone signs up, gets a secret string, wires it into code, and a card gets charged at the end of the month. An autonomous agent has none of that scaffolding — no email to verify, no card to enter, no person to approve the invoice. Per-request payment from the agent's own wallet removes the one step that always needed a human. Crypto Briefing summed the new requirement up as "just a wallet and a penny."
That's the shift worth marking: the agent becomes the paying customer, not its operator. Pricing stops being a subscription a person manages and becomes a cost the agent pays, per call, as it works.
The plumbing — and who else is in the race
The payment layer here is Alchemy's AgentPay, which [entered private beta in April 2026](https://cryptobriefing.com/0x-swap-api-ai-agents-usdc/). It's protocol-agnostic, takes no custody of funds, and Alchemy lists it as compatible with Coinbase, Stripe, Visa, Mastercard, and Circle. That compatibility list is the tell: agentic payments isn't one settled standard yet — it's a standards bake-off. x402 (originally out of Coinbase) is one entry; Google's [Agent Payments Protocol](/resources/agent-payments-protocol-ap2) and [Visa's Trusted Agent Protocol](/resources/visa-trusted-agent-protocol-tap) are others. We track the contenders side by side on the [payments use-case page](/use-cases/payments), with [x402](/resources/x402) and [Alchemy](/resources/alchemy) listed as resources.
Is anyone actually using this? The x402 network processed 75.41 million transactions worth $24.24 million over the past 30 days, [per The Defiant](https://thedefiant.io/news/defi/0x-swap-api-ai-agents-usdc-payment-x402). That's real traffic — and also a reminder that the average payment is a fraction of a dollar, which is exactly the point. Micropayment rails only earn their keep on micro-amounts. For the larger question of who ultimately covers the cost of agent activity, Keyrock and Coinbase's ["Who Pays the Agent?" report](/resources/keyrock-coinbase-who-pays-the-agent-report) is the read.
What this is — and what it isn't
Per-request USDC access is a billing model, not a safety claim. 0x is exposing pricing and execution to autonomous callers; it is not vouching that any agent calling it is trustworthy, and neither are we. "The payment cleared" tells you the money moved — nothing about whether the agent on the other end should be trusted with funds. Keep those two ideas apart. It's the whole reason SatoHub's [Sato Score](/sato-score) measures how open and verifiable a resource is, separately from whatever it claims about itself.
What to watch
Three things. First, whether x402 settlement stays on Base and Solana or spreads as more APIs adopt it. Second, whether the standards contest — x402 vs AP2 vs Visa's TAP — converges or fragments; agents would rather not implement four different payment handshakes to shop four APIs. Third, whether per-call pricing produces the behavior it implies: agents that comparison-shop APIs in real time and pay only for what they use. The penny is small. The behavior it makes possible is not.