For x402 sellers and agent builders

How x402 works

x402 lets a program pay for an HTTP request in the request itself: no account, no API key, no checkout. The server answers 402 Payment Required with a price, the client signs a payment and asks again, and a facilitator checks and settles it on a blockchain. Pick a payment flow and step through one request below.

Verify first, run the request, then settle. Money moves only after the work succeeds. Definition

Clientbuyer or agentResource serversellerFacilitatorverifies and settlesNetworkledger1 GET /resource2 402 + PAYMENT-REQUIRED3 retry + PAYMENT-SIGNATURE4 POST /verify5 runs the requeston-chain tx6 POST /settle $7 200 + PAYMENT-RESPONSE
Step 1 of 7

Step 1

The client asks, with no payment

An agent or app requests the resource like any other HTTP call. It does not need an account, an API key or to know the price in advance.

Glossary · x402 v2 specification, section 2, step 1

GET /api/x402/v1/brief HTTP/1.1
Host: www.blockchainiq.co
Accept: application/json

Our own endpoint

The three headers

Over HTTP, everything x402 adds travels in three headers, each a base64-encoded JSON object.

HeaderDirectionCarries
PAYMENT-REQUIREDServer to client, with HTTP 402PaymentRequired: the resource and the accepted payment options
PAYMENT-SIGNATUREClient to server, on the retryPaymentPayload: the option chosen and the signed authorization
PAYMENT-RESPONSEServer to client, with the resourceSettlementResponse: success, network, payer, transaction hash
  1. 200 Paid and served: the resource, with PAYMENT-RESPONSE
  2. 402 Payment required, or the payment failed verification or settlement
  3. 400 Malformed payment payload or requirements
  4. 500 Server error while processing the payment

A browser app on another site can read PAYMENT-REQUIRED only if the server lists it in Access-Control-Expose-Headers. The 402 Inspector checks that, and every field of a live challenge.

Decode a header

Paste the value of any x402 header to see the JSON inside it.

Decoded in your browser; nothing you paste leaves this page.

When a payment fails

A facilitator returns a reason in invalidReason (verify) or errorReason (settle). The common ones, from section 9 of the specification:

  1. insufficient_funds The payer's wallet does not hold enough of the token.
  2. invalid_exact_evm_payload_authorization_valid_before The signed authorization has expired.
  3. invalid_exact_evm_payload_authorization_valid_after The authorization is not valid yet.
  4. invalid_exact_evm_payload_authorization_value_mismatch The signed amount is not exactly the amount required.
  5. invalid_exact_evm_payload_recipient_mismatch The authorization pays a different wallet from payTo.
  6. invalid_exact_evm_payload_signature The signature does not check out.
  7. invalid_network The facilitator does not support that network.
  8. unsupported_scheme The facilitator does not support that scheme.
  9. settlement_pending The transfer was broadcast but not yet confirmed. Not final: check the transaction hash before retrying.

Go further

  1. Every term on this page: x402 glossary.
  2. Check your own endpoint: 402 Inspector.
  3. Daily grades for every listed seller: x402 Conformance Index.
  4. Try a real paid call at $0.01: Blockchain IQ for agents.
  5. The source: x402 v2 specification and its HTTP transport.

General education, not investment, legal or tax advice. The protocol is young and changes: check the current specification before you build on a detail. Read 11/19/2026.