HTTP 402 & x402: How AI Agents Pay for Content

HTTP 402 Payment Required is a long-reserved HTTP status code that can signal a resource is behind payment, but it has no single standardized behavior across the web. The newer x402 protocol turns that dormant status code into a practical payment handshake for APIs and AI agents, especially for micropayments and pay-per-use access.^[3][6]

HTTP 402: what it is and what it is not

HTTP 402 is reserved for future use in the HTTP specification and remains nonstandard in practice.^[3] MDN notes that no browser has native support for a special 402 flow, and implementations vary widely in how they use it.^[3] In the wild, some services use 402 as a generic payment failure or subscription problem indicator, not as a true protocol for completing payment.^[1][3]

For developers, that means a raw 402 response usually requires reading the provider’s documentation or response body to understand whether the issue is an expired subscription, failed card, quota overage, or a payment gate.^[1][3]

What x402 adds

x402 is an application-layer payment protocol built around HTTP 402 to make payment requirements machine-readable and retryable.^[5][6] In the x402 flow, a server returns a 402 response with payment details, such as amount, asset, destination, and acceptable payment options, so a client can pay programmatically and resend the request.^[5][6]

Coinbase’s x402 documentation describes this as a way to enable API-native payments, micropayments, and machine-to-machine payments without account creation or traditional billing flows.^[6] The protocol is especially aimed at web services that want to expose paid endpoints directly over HTTP.^[6]

Why AI agents care

AI agents need to buy discrete actions: API calls, data, compute, and content access. Traditional billing assumes a human with an account, checkout flow, and sometimes CAPTCHA, which does not fit autonomous or high-frequency agent workflows.^[7] x402 is designed to give agents a wallet-native payment primitive they can invoke inside a request-response cycle.^[5][6]

That makes x402 relevant to pay-per-crawl and other retrieval use cases: a crawler or agent can discover that content is paid, receive the terms in 402, pay, and continue without manual intervention.^[5][6]

Current practical view

Today, HTTP 402 by itself is mostly an informational signal unless a service defines its own semantics.^[1][3] x402 is the attempt to standardize a concrete payment flow on top of that status code, using crypto wallet rails and signed authorization to keep the interaction HTTP-native.^[5][6]

Key takeaways

• HTTP 402 is reserved and still nonstandard; different services use it differently.^[3]
• x402 turns 402 into a programmable payment handshake for HTTP APIs and agents.^[5][6]
• The main use case is micropayments and pay-per-use access without human-centered checkout flows.^[6][7]
• For AI agents, x402 is most useful when a task requires autonomous payment for API access, data, or crawl-time content.^[5][6]

Synthesized by the AISA LLM layer with live web sources (AISA Perplexity + Tavily APIs). 2026-06-15.