x402 Explained: HTTP-Native Micropayments for AI Agents (With Real Code)

As autonomous AI agents shift from isolated experimental scripts to active participants in the digital economy, they face a fundamental bottleneck: payments.

Traditional SaaS monetization relies on credit cards, monthly subscriptions, and manual API key generation. These patterns are designed for humans. An autonomous agent spinning up dynamically to complete a task cannot sign up for a SaaS tier, nor should it commit to a $20/month subscription for a service it only needs to call three times.

To achieve true autonomy, agents require machine-to-machine, pay-per-use micropayments.

The x402 protocol solves this by reviving the underutilized HTTP 402 Payment Required status code, pairing it with low-cost Layer 2 (L2) blockchains like Base to enable stateless, inline micro-transactions.

---

The x402 Handshake Flow

The x402 flow is a simple, stateless challenge-response mechanism built directly over HTTP:

[Agent]                                                [API Gateway]
   |                                                        |
   | 1. POST /v1/tools/web-search (No Payment Header)       |
   |------------------------------------------------------->|
   |                                                        |
   | 2. HTTP 402 Payment