Also: agent-to-agent, Agent2Agent
Agent-to-agent communication. The spec lists A2A as a transport, so one agent can charge another for work using the same payment objects.
Agents
90 terms across 9 topics for anyone building, selling to or buying with AI agents over x402: the HTTP 402 payment standard. Protocol terms cite the specification; the last topic explains how Blockchain IQ measures the x402 market. Free to read. For the live data, see the Conformance Index and the pay-per-call API.
Dashed arrows are the server's replies. Source: x402 v2 specification, sections 2, 6.1 and 7.
Filled chips are the steps that commit payment. Whatever the flow, at least one check, a verify or a settle, runs before the resource does. Source: x402 v2 specification, section 6.1.
90 terms
Also: agent-to-agent, Agent2Agent
Agent-to-agent communication. The spec lists A2A as a transport, so one agent can charge another for work using the same payment objects.
Also: accepted requirements
The field in a PaymentPayload that holds the PaymentRequirements object the client chose from the accepts list. The server checks that it matches an option it offered.
See also: accepts, PaymentPayload
Also: accepts array
The list of payment options in a PaymentRequired object. A seller can offer several, for example the same price on two networks. The client chooses one it can fulfill and echoes it back as accepted in its payload.
See also: PaymentRequirements, accepted, PaymentRequired
Also: autonomous agent, agentic buyer
Software that pursues a goal by calling tools and services on its own. x402 lets an agent pay for what it needs mid-task, with automatic payment handling, resource discovery and spending controls that implementations provide.
See also: Client, Budget management, MCP
Also: price, maxAmountRequired
The price in atomic token units, written as a string. For USDC, which has 6 decimals, "10000" is $0.01. Under the upto scheme the amount is the most the client authorizes, and the settled amount may be lower.
See also: Atomic units, upto, USDC
Also: token, payment token
What the payment is made in: a token contract address on chain networks, or an ISO 4217 currency code for fiat. On Base the usual asset is USDC.
See also: USDC, PaymentRequirements, Atomic units
Also: transfer method
A reserved key in extra naming how value is authorized or moved for a given scheme and network. The spec's examples are eip3009 versus permit2 on EVM exact, and sequence versus ticketSequence on XRPL exact. The allowed values are defined by each mechanism.
Also: base units, smallest units
The smallest indivisible unit of a token, used so amounts are whole numbers. USDC has 6 decimals, so 1 USDC is 1,000,000 atomic units and one cent is 10,000.
Also: authorize and capture
A scheme named in the specification, borrowing the card-world idea of authorizing first and capturing later. Its rules are defined under specs/schemes in the repository; check there before implementing.
See also: Scheme, escrow flow
Also: verify then settle
The default flow: verify, run the resource, then settle. Verification is read-only, so no funds move until the work has succeeded. When a seller offers this and a pre-settlement flow for the same request, clients should prefer it.
See also: Payment flow, /verify, /settle
Also: eip155:43114, Avalanche C-Chain
An EVM network listed in the spec's examples, as eip155:43114 for mainnet and eip155:43113 for the Fuji testnet.
See also: EVM networks, CAIP-2
Also: Base mainnet, eip155:8453
A low-fee Ethereum layer-2, with CAIP-2 identifier eip155:8453. It is the network where most paid x402 calls settle, in USDC.
See also: CAIP-2, USDC, Base Sepolia
Also: eip155:84532, Base testnet
Base's test network, identified as eip155:84532. The spec's examples use it so a payment can be tried with no real money.
Also: batch settlement
A scheme named in the specification for settling many small payments together instead of one transaction each. Its exact rules are defined under specs/schemes in the repository; check there before implementing.
See also: Scheme, Micropayment
Also: x402 Bazaar, discovery layer
The marketplace ecosystem for x402: a way for clients to find paid resources by category, provider or payment requirements. In the spec it is both a concept and an extension, and a facilitator can serve a Bazaar listing of the resources it has seen.
See also: Discovery API, Extension, ResourceInfo
Also: spend controls, spending limits
Limits on what an agent may spend: per call, per day, per seller. The core spec treats it as implementation-specific rather than part of the protocol, so safeguards come from the client library or wallet in use.
See also: AI agent, Client, maxTimeoutSeconds
Also: x402 buyer, payer wallet
A buyer is the wallet that pays for an x402 call. Many buyers are autonomous agents, and the same operator can control several buyer wallets. On chain a buyer shows up as the payer on the settlement transaction.
See also: Client, AI agent, SettlementResponse
Also: chain ID format, network identifier
The Chain Agnostic format for naming a network as namespace:reference. In x402 v2 every network is written this way, for example eip155:8453 for Base mainnet, so one field works across EVM, Solana and non-blockchain rails such as ach:us.
Also: buyer, x402 client, payer
The client is any application or agent that requests a protected resource and pays for it. It reads the challenge, chooses a payment option it supports, signs an authorization and sends it with the retried request.
See also: Resource server, AI agent, PaymentPayload
Also: CDP, CDP facilitator
Coinbase's developer platform, which operates an x402 facilitator and publishes a discovery list of paid resources. Blockchain IQ's roster reads that list daily, which is why CDP-listed endpoints form the largest part of our seller count.
See also: Facilitator, Bazaar, Roster
Also: no longer listed
When a catalogue stops listing an endpoint it used to include. We mark such endpoints rather than delete them, because a delisted endpoint may still work or may come back.
See also: Roster, Marketplace listing
Also: x402 discovery
The HTTP interface through which clients list and search x402 resources. Discovered resources may use any x402-supported transport even though the discovery interface itself is HTTP.
See also: /discovery/resources, /discovery/search, Bazaar
Also: list resources
The endpoint that lists discoverable resources. It filters by type, payTo, scheme, network and extensions, and pages with limit (1 to 100, default 20) and offset.
See also: Discovery API, payTo
Also: search resources
The endpoint for searching resources by text. Its semantics are defined in the Bazaar extension specification, since search behavior is extension-specific.
See also: Discovery API, Bazaar
Also: usage-based pricing, authenticated pricing
Setting the price per request from who is asking or how much work is needed, which x402 supports because the price is returned fresh in each 402. Examples are discounts for authenticated users and prices that scale with usage.
See also: Pay-per-call, upto, Sign-In with Ethereum (SIWE)
Also: Transfer With Authorization, transferWithAuthorization
An Ethereum token standard that lets a holder approve a transfer with an off-chain signature, so someone else can submit it and pay the gas. The x402 exact scheme on EVM uses it with USDC: the payer signs, the facilitator broadcasts. The authorization carries from, to, value, validAfter, validBefore and a 32-byte nonce.
See also: exact, EIP-712, Nonce, Gas sponsorship, validAfter / validBefore
Also: typed structured data signing
The Ethereum standard for signing structured, human-readable data rather than opaque bytes. The signature in an EVM exact payment is an EIP-712 signature over the EIP-3009 authorization.
See also: EIP-3009, PaymentPayload
Also: deposit then final charge
Settle a deposit or ceiling, run the resource, settle again with the final charge, respond. Because /settle can run more than once for one payment, a scheme using escrow must say how the facilitator tells the steps apart.
See also: Payment flow, /settle, upto
Also: Ethereum-compatible chains, eip155
Ethereum and the chains that run the same virtual machine. Their CAIP-2 namespace is eip155 and the number is the chain ID. x402 uses ERC-20 tokens that implement EIP-3009, with USDC the main example.
Also: exact scheme
The scheme where the client pays precisely the stated amount. On EVM networks it uses a signed EIP-3009 authorization, so the payer signs and a facilitator submits the transfer. It is the scheme most x402 endpoints use today.
Also: x402 extension, extensions object
A modular, optional add-on carried in the extensions field. Each extension has an info object from the server and a JSON Schema describing it. Servers advertise them in PaymentRequired and clients echo them back, adding to the info but never deleting or overwriting it. Bazaar discovery is one.
See also: Bazaar, EXTENSION-RESPONSES header, PaymentRequired
Also: extension responses sidechannel
A facilitator-to-server sidechannel: a base64-encoded JSON object, keyed by extension name, reporting how extensions were processed. It travels in a header, not in the JSON body, and is never forwarded to buyers.
See also: Extension, Facilitator
Also: extra field
An optional object in PaymentRequirements for scheme-specific data, such as a token's name and version for signing. Two keys are reserved by the protocol, assetTransferMethod and paymentFlow; the rest belong to the scheme.
See also: assetTransferMethod, Payment flow, PaymentRequirements
Also: x402 facilitator, payment facilitator
A service that checks and settles x402 payments so a seller does not have to run blockchain infrastructure. It exposes three HTTP endpoints, /verify, /settle and /supported, and a seller can use a hosted facilitator or run its own.
See also: /verify, /settle, /supported, Self-hosted facilitator, Gas sponsorship
Also: gasless payment, facilitator pays gas
Paying the network fee on the payer's behalf. Because an EIP-3009 payment is a signature rather than a transaction, the facilitator can submit it and cover the gas, so the buyer needs only the payment token.
See also: EIP-3009, Facilitator
Also: 402, 402 status code
HTTP 402 is a status code reserved since the early web for "payment required" and almost never used until x402 gave it a job. In x402 the server returns it with the price and the accepted ways to pay; a client that can pay answers with a signed payment on the next request.
See also: x402, PaymentRequired, Payment challenge
Also: insufficient funds error
The standard error code returned when the payer does not hold enough of the token to cover the amount. It can come back from /verify (invalidReason) or from /settle (errorReason).
Also: invalid signature error
The error code for an EVM exact payment whose signature is invalid or was made incorrectly. Related codes flag a recipient mismatch, a value that does not match the required amount exactly, and an authorization that is not yet valid or has expired.
See also: exact, EIP-712, PaymentPayload
Also: malformed payload error
The error code for a payment payload that is malformed or holds invalid data. Its neighbors are invalid_payment_requirements, invalid_scheme, unsupported_scheme, invalid_network and invalid_x402_version.
See also: PaymentPayload, Scheme
Also: production network
A live network where tokens have real value. Counting only mainnet sellers matters when measuring x402, because test-network endpoints cost nothing to list.
Also: catalogue listing
An entry in a third-party catalogue of x402 services. Some catalogues list paid URLs and others list only wallets or hosts, so a listing is a lead to check rather than proof of a working endpoint.
Also: payment timeout
The longest time the seller allows for the payment to complete. Together with validAfter and validBefore on the authorization it keeps a signed payment from staying usable indefinitely.
See also: validAfter / validBefore, PaymentRequirements
Also: Model Context Protocol
The Model Context Protocol, a standard for giving AI models tools and data. x402 payment objects can be carried over MCP, so an agent can pay for a tool call the way it would for an HTTP request.
Also: small payment, sub-dollar payment
A micropayment is a payment far smaller than a card payment can economically carry, often a cent or less. Stablecoin transfers on low-fee networks make them workable, which is what lets an API charge per call.
See also: Pay-per-call, USDC, Stablecoin
Also: 32-byte nonce
A random single-use value inside each EIP-3009 authorization. The token contract records used nonces, so the same authorization can never be executed twice.
See also: Replay attack, EIP-3009
Also: per-request pricing, usage-based API pricing
Pay-per-call means each request is priced and paid for on its own, with no account, subscription or API key. x402 makes it practical by putting the price in the 402 response and settling the payment as part of the request.
See also: Micropayment, Dynamic pricing, x402
Also: 402 challenge, 402 response
A payment challenge is the server's 402 response: a price list, in the form of a PaymentRequired object, telling the caller what to pay and how. A "valid 402" is one that carries a well-formed challenge. The client picks one accepted option and retries with a payment attached.
See also: PaymentRequired, accepts, Valid 402
Also: payment flow model, paymentFlow
The order of checking, settling and doing the work for one request. The spec defines three: authorization, upfront and escrow. A mechanism declares its default, and when the default is not authorization the requirements must say so in extra.paymentFlow. At least one check, a verify or a settle, always runs before the resource executes.
See also: authorization flow, upfront flow, escrow flow, extra
Also: payment required header
The HTTP response header that carries the base64-encoded PaymentRequired object, the canonical place a v2 server puts its price on HTTP.
See also: PaymentRequired, PAYMENT-SIGNATURE header
Also: payment signature header
The HTTP request header a v2 client uses to send its payment. The spec's own example error is "PAYMENT-SIGNATURE header is required", which is what a server says when a request arrives without payment.
See also: PaymentPayload, PAYMENT-REQUIRED header
Also: payment authorization, signed payment
What the client sends back to pay: the x402Version, the resource, the accepted PaymentRequirements it chose, a scheme-specific payload (for example a signature and authorization) and any extensions. It is the signed promise to pay, not the settled payment.
See also: accepted, PAYMENT-SIGNATURE header, EIP-3009, PaymentRequirements
Also: payment required object
The object a resource server returns when payment is needed. It holds x402Version, an optional error message, a resource description, an accepts list of payment options and optional extensions. On HTTP it is carried base64-encoded in the PAYMENT-REQUIRED response header.
See also: PaymentRequirements, accepts, ResourceInfo, PAYMENT-REQUIRED header
Also: payment option, price entry
One acceptable way to pay, an entry in the accepts list. It names the scheme, the network, the amount in atomic units, the asset, who gets paid (payTo), how long the payment may take (maxTimeoutSeconds) and optional extra data.
See also: accepts, Scheme, amount, asset, payTo, maxTimeoutSeconds
Also: seller address
The payTo address an endpoint asks to be paid at. It is how we group endpoints by seller: many URLs on many hosts can share one payout wallet.
Also: payout wallet, recipient wallet, seller wallet
The address that receives the payment, or a role constant such as "merchant". It identifies the seller on chain, which is why payTo is the field most often used to group endpoints by who earns from them.
See also: Seller, PaymentRequirements, Payout wallet
Also: Permit2 transfer
A shared token-approval contract that can authorize transfers by signature for tokens that lack EIP-3009. The spec lists permit2 as an assetTransferMethod alongside eip3009 on EVM exact.
See also: assetTransferMethod, EIP-3009
Also: unpaid probe, unpaid GET
One unpaid request to an endpoint to see whether it answers with a payment challenge. A probe spends nothing and settles nothing; it only shows what the endpoint says it would charge.
See also: Valid 402, Roster, Payment challenge
Also: replay protection
Reusing a valid signed payment to pay again or to pay somewhere else. x402 guards against it with a unique 32-byte nonce per authorization, contract-level nonce tracking, explicit validity windows and signature checks.
See also: Nonce, validAfter / validBefore, EIP-3009
Also: seller server, API server, merchant server
The resource server is the service that charges for a protected resource such as an API, a dataset or content. It issues the payment challenge, checks the payment (itself or through a facilitator) and returns the resource once payment is good.
See also: Client, Facilitator, Seller, payTo
Also: resource object
The part of a challenge that describes what is being sold: its URL, plus optional description, MIME type, serviceName (printable ASCII, 32 characters at most), up to five discovery tags and an icon URL.
See also: PaymentRequired, Bazaar, serviceName and tags
Also: x402 roster, seller roster
Blockchain IQ's daily list of x402 endpoints, built from public catalogues and our own checks. Each run reads the catalogues, probes the listed URLs, records which still answer with a valid 402, and marks endpoints that a catalogue stopped listing.
See also: Probe, Valid 402, Delisting, Marketplace listing
Also: payment scheme
A scheme defines how a payment is formed, validated and settled on a network. The spec names exact, upto, batch-settlement and auth-capture, each specified per network under specs/schemes. The scheme field in a payment option tells the client which one applies.
See also: exact, upto, batch-settlement, auth-capture
Also: own facilitator
A facilitator run by the seller. The spec allows resource servers to delegate blockchain operations to trusted third parties or host the endpoints themselves; hosting removes a dependency but means running settlement infrastructure.
See also: Facilitator, Resource server
Also: x402 seller, service provider
A seller is the party that earns from an x402 endpoint: the operator behind a resource server and the wallet its payments go to. Counting sellers is harder than it sounds, because one seller may run many hosts and one host may list several wallets.
See also: Resource server, payTo, Roster
Also: service tags
Optional ResourceInfo fields that make a listing findable: a short service name and up to five tags, each printable ASCII and at most 32 characters. Good ones are the difference between being discovered and being invisible.
See also: ResourceInfo, Bazaar
Also: settle endpoint, POST /settle
The facilitator endpoint that durably commits a payment, for example by broadcasting a transaction. Its request has the same shape as /verify. It may run more than once for one payment, and under upto the amount to settle is the one used rather than the ceiling.
See also: Facilitator, SettlementResponse, escrow flow
Also: on-chain settlement
The step that actually moves value: the signed authorization is turned into a transaction, or another durable commitment, and recorded on the ledger. Settlement is distinct from verification, and for some methods it need not be an on-chain write.
See also: /settle, /verify, Payment flow
Also: pending settlement error
A non-terminal result meaning the transaction was broadcast but its confirmation could not be established, for example after a node timeout. The transaction may still confirm, so the response must carry the broadcast hash and network and the caller should reconcile on chain before retrying.
See also: SettlementResponse, /settle
Also: settle response, payment receipt
The receipt after settlement: success, the transaction hash, the network (CAIP-2), the payer and optionally the amount settled and an errorReason. The transaction is an empty string if nothing was broadcast, and must be non-empty when the reason is settlement_pending.
See also: /settle, settlement_pending, CAIP-2
Also: SIWE
A standard for proving control of an Ethereum address. The spec names it as a way to combine authentication with payment, for instance giving verified users discounted prices.
See also: Dynamic pricing, Client
Also: facilitator signer addresses
The addresses a facilitator uses to submit transactions, published in /supported as a map from CAIP-2 patterns (such as eip155:*) to addresses. They are how on-chain observers recognize a facilitator's settlements.
See also: /supported, Facilitator, CAIP-2
Also: solana mainnet
A non-EVM network x402 supports. Its mainnet CAIP-2 identifier in the spec is solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp. Payments can use any SPL token or Token-2022 token.
Also: Token-2022
Solana's token standard, with Token-2022 as its newer program. The spec states that any SPL or Token-2022 token can be used for payment on Solana.
Also: dollar token
A token designed to hold a fixed value, usually one US dollar. x402 sellers price in stablecoins so the price stays steady between the 402 and the settlement.
See also: USDC, Micropayment
Also: supported endpoint, GET /supported
The facilitator endpoint that lists which schemes, networks and extensions it supports, plus its signer addresses. A seller reads it to know what it can offer; a researcher reads it to see which chains a facilitator covers.
See also: Facilitator, Signers, Scheme, CAIP-2
Also: test network
A network with valueless tokens for development, such as Base Sepolia. Endpoints that accept only testnet payments are real x402 implementations but earn nothing.
See also: Mainnet, Base Sepolia
Also: transport layer
The channel that carries x402 messages: HTTP headers, MCP messages, A2A or any request-response system. Each transport specifies where the payment-required and payment objects sit; the objects themselves do not change.
See also: Transport-agnostic, PAYMENT-REQUIRED header, MCP
Also: transport independent
x402 separates what is said (types), how a payment is formed (logic per scheme and network) and how it is carried (representation per transport). So the same payment objects can ride on HTTP headers, MCP messages or agent-to-agent calls.
Also: trust-minimized payments
Designing so neither side has to trust the other: the payer signs a bounded authorization and the facilitator can move only that exact amount to that exact recipient. The facilitator is trusted to settle and report honestly, not to hold the buyer's funds.
See also: Facilitator, EIP-3009, Replay attack
Also: settle first
Settle, run the resource, respond. The payment is committed before the work, giving the seller finality first; /verify is not part of this ordering. Required on networks that have no way to pull a payment later.
See also: Payment flow, /settle
Also: upto scheme, usage-based scheme
A scheme where the amount in the requirements is a ceiling. The client authorizes up to that amount and the seller settles what was actually used, which suits metered work such as token-based pricing. At settle time the amount field means the amount to settle.
Also: USD Coin
A dollar-pegged stablecoin and the dominant x402 payment token. It implements EIP-3009 on EVM networks and has 6 decimals, so prices are quoted in whole cents and fractions of a cent.
See also: Stablecoin, Atomic units, EIP-3009
Also: well-formed 402
A 402 response that contains a usable payment challenge, as opposed to a bare 402 status, an error page or a timeout. Counting valid 402s separates endpoints that really sell from ones that merely exist.
See also: Payment challenge, Probe, Roster
Also: authorization window
Unix timestamps that bound when an authorization can be used. Before validAfter it is rejected as not yet valid; after validBefore it has expired. The short window limits the damage if a signature leaks.
See also: Replay attack, maxTimeoutSeconds, EIP-3009
Also: verify endpoint, POST /verify
The facilitator endpoint that checks a payment authorization without executing it. It is read-only: it may validate state but must not commit any. It receives the payload and the requirements and returns isValid, or an invalidReason such as insufficient_funds.
See also: Facilitator, VerifyResponse, authorization flow
Also: verification result
A facilitator's answer to /verify: isValid, an invalidReason when it is not valid, the payer and optional extensions. It means the authorization checks out, not that money has moved.
See also: /verify, PaymentPayload
Also: x402 protocol
x402 is an open payment standard built on the HTTP 402 Payment Required status code. A server that wants payment answers a request with its price; the client signs a payment, retries, and gets the resource. It defines message formats and flows that can run over HTTP, MCP and other transports, with different payment schemes and networks.
See also: HTTP 402 Payment Required, Resource server, Client, Facilitator, Payment flow
Also: x402 repository
The group that stewards the open x402 specification and reference implementations. The spec points readers to the repository at github.com/x402-foundation/x402, where the specification, scheme definitions and extension specs live.
Also: protocol version 2, x402Version 2
Version 2 of the protocol, dated 12/09/2025 in the spec's history. Compared with v1 it moves networks to CAIP-2 identifiers, restructures the PaymentRequired and PaymentPayload objects, separates ResourceInfo and adds protocol extensions. The version number travels in every message as x402Version.
See also: CAIP-2, PaymentRequired, PaymentPayload, Extension
Also: XRP Ledger
The XRP Ledger, which the spec names when explaining assetTransferMethod: the XRPL exact scheme uses methods called sequence and ticketSequence.
See also: assetTransferMethod, Scheme
General education, not investment, legal or tax advice. The protocol is young and changes: definitions follow version 2 of the x402 specification, and where a scheme or extension is defined elsewhere in the specification repository we say so rather than guess. Check the spec before you build on a detail.
New research, notable moves, and what we’re watching. No more than a few emails a month, and nothing else — we don’t sell or share your address.