Is There an x402 Token?
No. x402 is a payment protocol that revives a reserved HTTP status code, not an asset. There is no native token, nothing to buy and nothing to hold. Payments made through it settle in whatever asset the server asks for, which in practice is usually a dollar-referenced stablecoin.
What x402 actually is
HTTP defines a status code, 402, reserved decades ago for payment and left unimplemented. x402 is a convention for finally using it.
The flow is small. A client requests a resource. The server responds 402 with machine-readable terms: how much, in what asset, to what destination, and how long the quote is valid. The client settles, retries with proof of payment, and the server serves the resource.
That is the entire protocol. It is a way for a server to say payment required in a form software can act on without a human reading a pricing page.
Notice what is absent. There is no ledger belonging to x402, no validator set, no governance, no treasury and no unit of account of its own. It specifies how a price is communicated and how proof of payment is presented. What actually moves is whatever asset the server named.
So there is nothing for a token to do. A protocol token would have to be inserted between the buyer and the seller for no reason, and it would make the system worse by adding a volatile intermediary to a payment that both parties wanted denominated in something stable.
Why the question keeps coming up
The expectation is reasonable given the surrounding landscape. Most things in this space that call themselves protocols do have tokens, often because the token funded the development or because it governs a network that needed one.
x402 does not need one because it is not a network. It is a message format layered on infrastructure that already exists: HTTP for the request, an existing chain for settlement, an existing stablecoin for denomination. Nothing new had to be bootstrapped, so nothing new had to be issued.
This creates a predictable pattern worth naming plainly. When a protocol becomes well known and has no token, tokens appear claiming association with it. They are unconnected to the specification, to anyone maintaining it, and to the payments actually flowing through implementations.
If you encounter something offered as an x402 token, the useful assumptions are that it is not issued by the protocol, that holding it does not affect your ability to send or receive x402 payments, and that its price has no relationship to protocol adoption.
There is nothing to buy in order to use x402. You need an asset the counterparty accepts, which is the same requirement as any other payment.
What you do need
An address that can hold the settlement asset, a balance in it, and a small amount of the network's native asset to pay transaction fees. On Base that means USDC plus enough ETH for gas. For an agent it also means bounded spending authority, so the balance is delegated rather than fully exposed, which is what session keys provide.
What settles instead
Because the protocol is asset-agnostic, the practical question moves to what a server should ask for, and the answer is narrower than it first appears.
Machine payments need an amount agreed now to mean the same at settlement and again at reconciliation. Spending caps, per-call pricing and accounting all assume a unit that holds still. A volatile asset makes every one of those unreasonable, because a budget denominated in something that moves is not a budget.
That rules out project tokens and native network assets as the denomination, even though the native asset is still required for fees. It leaves dollar-referenced stablecoins, which is why implementations converge there without the specification mandating it.
The remaining choice is which chain the settlement happens on, and that is a decision about finality time, fee predictability and stablecoin liquidity rather than about ideology. CryptoCadet settles in USDC on Base for those reasons: fees low enough that small per-call amounts are not absurd, and finality fast enough that a client is not waiting on a payment before receiving a response.
If someone tells you that using x402 requires acquiring a particular asset beyond the one the seller asked for, they have described something other than the protocol.
Frequently asked questions
- Is there an x402 token or coin?
- No. x402 is a payment protocol built on the reserved HTTP 402 status code. It has no native asset, no ledger of its own and no treasury. Payments settle in whatever asset the server specifies in its payment challenge, most commonly a dollar-referenced stablecoin.
- Can you buy x402?
- There is nothing to buy. Using the protocol requires an asset the counterparty accepts, an address that can hold it, and a small amount of the network's native asset for fees. Anything offered for sale as an x402 token is unconnected to the specification or to payments flowing through it.
- Why does x402 not have a token when other protocols do?
- Because it is not a network. It is a message format layered on infrastructure that already exists: HTTP for the request, an existing chain for settlement and an existing stablecoin for denomination. Nothing had to be bootstrapped, so nothing had to be issued.
- What asset do x402 payments settle in?
- Whatever the server asks for, since the protocol is asset-agnostic. In practice implementations converge on dollar-referenced stablecoins, because machine payments need an amount that means the same at agreement, settlement and reconciliation, which a volatile asset cannot provide.