Skip to main content
x402 is an open payment standard that reuses the existing HTTP 402 Payment Required status code to let a server ask for payment, and let a client pay, inside an ordinary HTTP request/response cycle. It turns a payment into something a client can satisfy as easily as it follows a redirect — no checkout page, account signup, or API-key dance required. Hedera contributes its own exact payment scheme and a reference implementation to the official x402 repository, so applications and AI agents can settle payments in HBAR or HTS tokens over x402 with the speed and low, predictable fees of the Hedera network.
For the background story and Hedera’s perspective on why this matters, read the announcement: Hedera and the x402 Payment Standard.

​
What x402 actually is (and what it is not)

x402 is best understood as the missing payment layer of the web: HTTP can move information instantly, but it has never had a native, standardized way to move money. x402 fills exactly that gap — and nothing more. It is easy to over-read x402 as a magic switch that suddenly lets “agents use crypto” for anything. The real scope is much narrower then that and spans multiple use-cases.

What x402 IS

  • An HTTP-native standard for a single, discrete request → pay → response handshake
  • Stateless and per-request — each payment is self-verifying, with no billing session or subscription
  • Settlement-agnostic — works across chains and assets; on Hedera it settles in HBAR or HTS tokens
  • A shared rulebook so any wallet or service can negotiate value the same way it negotiates data

What x402 is NOT

  • Not a blockchain or a new payment network — it lives on top of existing rails
  • Not a custodial processor — facilitators verify and submit, but can never move funds without a signed authorization
  • Not for streaming or multi-hop routing — it is optimized for discrete request/response cycles, not continuous value flows
  • Not a general “agentic wallet” — it is one well-scoped primitive, not an autonomy framework

​
Who uses it and what it is useful for

x402 shines whenever value needs to change hands per request, at machine speed, without a human in the loop:
  • AI agents paying for API calls, context, datasets, inference, or tool use on demand
  • Paid APIs and per-request metering — bill for exactly what is consumed instead of selling subscriptions or API keys
  • Pay-per-view digital content — articles, reports, research papers, sensor feeds, OCR, translations
  • Micropayments at internet scale — amounts too small to justify a checkout flow or a card fee
Because the payment is just an HTTP exchange, it composes cleanly with the web technologies you are already familiar with — reverse proxies, CDNs, TLS, and REST or GraphQL APIs.

​
Resources

Hedera and the x402 Payment Standard

Hedera’s announcement blog covering the what and why.

Hedera exact scheme spec

The authoritative definition of the Hedera scheme.

@x402/hedera reference implementation

The official TypeScript package for client and server.

x402 whitepaper

The protocol’s design and rationale.

x402: The Missing Payment Layer of the Web

Blocky Research’s deep-dive report on x402’s scope, users, and limits.

Blocky402 facilitator

An open x402 facilitator with Hedera support.