What is HTTP 402, and why does it matter?
The web was not really built with payments in mind, especially not for autonomous agents or machines. But with the rise of AI and decentralized finance (DeFi), the need for seamless, native digital payments has never been more urgent.
Coinbase x402 announced a new open protocol designed to let APIs, apps and AI agents pay instantly using stablecoins like USDC (USDC), all via the familiar HTTP protocol.
This isn’t just a product update. X402 revives a long-forgotten piece of internet infrastructure and reimagines it for a future powered by agentic systems and crypto.
HTTP status codes: A quick refresher
Understanding HTTP status codes helps clarify how the web communicates behind the scenes. Here are some key ones to know:
- HTTP 200 — OK: Standard response for successful HTTP requests.
- HTTP 401 — Unauthorized: Indicates the request requires user authentication; typically used when credentials are missing or invalid.
- HTTP 403 — Forbidden: The server understood the request, but it refuses to authorize it (often due to lack of permissions or access control).
- HTTP 404 — Not found: Indicates that the requested resource could not be found.
- HTTP 402 — Payment required: Originally intended to support digital payments directly within the protocol but left as a “reserved for future use” status code due to the lack of global payment infrastructure at the time.
- HTTP 500 — Internal server error: A generic error message when the server encounters an unexpected condition.
Although the creators of the web imagined a future where online services might request payments directly through the protocol, for decades, no one found a practical use for it. It sat dormant for over 25 years, with no widespread adoption or defined behavior.
Today, HTTP 402 is finally coming to life, thanks to Coinbase’s x402 protocol. X402 turns HTTP 402 from a placeholder into a real mechanism. It allows websites, APIs and services to signal that a payment is required before granting access to digital goods or services.
Unlike traditional payment systems, which rely on external redirects or complex integrations, x402 enables native, in-protocol payments using stablecoins directly over HTTP.
But why do x402 and the activation of HTTP 402 matter?
With machine-to-machine interactions, autonomous agents and AI-driven services on the rise, the internet needs a payment layer that is:
- Instant
- Programmable
- Interoperable
- Trust-minimized.
Activating HTTP 402 positions it as a key enabler for decentralized commerce, autonomous agents and crypto-native applications. It could become as foundational as HTTP 200 or 404 in a future where services charge micro-fees, stream value or sell access dynamically.
Coinbase x402: A native payment layer for the web
Coinbase’s x402 is an open protocol that allows websites and APIs to request and receive payments in stablecoins directly over HTTP. It works by using the existing HTTP infrastructure and augmenting it with a lightweight payment layer.
Here is the step-by-step process for machine-to-machine transactions using the x402 protocol:
- Client requests a paid resource: A client, such as an AI agent, app, or browser initiates a request to an x402-enabled server (e.g., an API, data set or digital service) that requires payment to access.
- The server responds with a 402 Payment Required: In response, the server returns an HTTP 402 status code, along with the payment details. This includes the amount to be paid, the supported token (such as USDC) and a payment payload or address to use.
- Client submits the payment: The client uses its crypto wallet to sign and submit the payment. This happens programmatically — no user interaction is needed, which enables fully automated or agentic payments. It resends the original request, this time including the encoded payment information in an X-PAYMENT HTTP header.
- The payment is verified and settled onchain: A payment facilitator service, such as Coinbase’s x402 Facilitator, checks the blockchain to verify that the payment has been made and confirmed.
- The server delivers the resource: Once the payment is validated, the server fulfills the request and returns the data or content. It also includes an X-PAYMENT-RESPONSE header confirming the success of the transaction.
In x402, payments happen over standard HTTP using two custom headers: X-PAYMENT and X-PAYMENT-RESPONSE. These headers allow seamless, automated payments between apps, agents and servers — without changing how HTTP works. It’s a simple yet powerful way to enable web-native, machine-to-machine commerce using stablecoins.
What makes x402 revolutionary is that it doesn’t require platforms, plugins or third-party integrations. It creates a native payment layer for the web itself, just like HTTPS added security or cookies enabled session…
cointelegraph.com