x402 in plain words
Think of a vending machine: you pick a product, the machine shows the price, you pay, and it hands over what you asked for. x402 does something similar on the web. A client asks for a resource (an API response, a file, a piece of data), the server answers with the 402 Payment Required code and the payment instructions, the client pays, and once the server verifies it, the client gets the resource.
The analogy has a limit: with x402 the one paying can be a program, not a person at a screen. The official documentation describes it as an open standard with native support for machine-to-machine payments, designed so AI agents can pay autonomously (x402 documentation). It is open source under the Apache-2.0 license and maintained by the x402 Foundation.
The flow, step by step
- The client (for example, an AI agent) asks the server for a resource.
- The server responds with 402 Payment Required and includes the payment instructions.
- The client prepares the payment and sends it along with a new request.
- The server verifies the payment, either directly or through a facilitator.
- If the payment is valid, the server delivers the resource.
This is a simplified example of the exchange, only to show the sequence. It is not the specification: the exact names and formats are in the official documentation.
Client -> Server : asks for the resource (for example, a report from an API)
Server -> Client : 402 Payment Required + payment instructions (amount, destination, network)
Client : prepares the payment and signs it with its wallet
Client -> Server : repeats the request with a header that carries the proof of payment
Server : verifies the payment (directly or with a facilitator)
Server -> Client : 200 OK + the resourcex402 versus a card and a balance with spending rules
x402 answers the question "how does payment happen". It does not answer the question "how much can an agent spend". They are different layers, which is why an agent that pays with x402 still needs spending limits applied outside of it.
| Aspect | x402 | Card | Balance with spending rules |
|---|---|---|---|
| What it solves | How a service charges and a client pays inside an HTTP request, with no human step | A familiar payment method, designed for people who shop | How much, to whom and when an agent can pay |
| What it does not solve | It does not decide how much the agent can spend or to whom | It was not designed for a program to pay autonomously on every request | It does not define the protocol the service uses to charge |
| Who sets the spending ceiling | No one, on its own: a layer of rules is needed | The issuer and whoever configures the card limits | A system the agent does not control |
| When it fits | Services that charge per request or per resource | Purchases from merchants that accept cards | As a control over either of the other two |
In practice you do not pick just one: x402 can be the channel the payment goes through, and spending rules the control that decides whether that payment is allowed.
What you need to pay with x402 from an agent
- A wallet with USDC. x402 is a crypto-native payment standard, so the agent needs funds in a compatible wallet.
- Spending limits. A cap per payment and a daily cap, applied in a system the agent cannot edit.
- Allowed destinations. A list of services the agent may pay; everything else is declined.
- Human approval. For large amounts or new destinations, a person confirms before the payment goes out. See the guide on approval over WhatsApp.
Risks worth keeping in mind:
- The agent can be tricked. Malicious text in a page or a response can lead it to pay for something it should not.
- A service can overcharge. The price is set by whoever responds with the 402; if the agent pays without comparing, it pays whatever is asked.
- Networks and their costs change. Network fees and confirmation times can vary from one moment to the next.
- Local regulation varies. Using digital assets has different tax and legal implications in each country; consult a professional.
Short glossary
- x402. An open payment standard that uses the HTTP 402 Payment Required code to charge for access to APIs and content.
- Facilitator. A service the server can use to verify the payment instead of doing it directly.
- USDC. A digital dollar that aims to hold a value of 1 dollar; that is the issuer goal, not a promise.
- Micropayment. A payment of a very small amount, for example for a single API request.
- AI agent that pays. A program built on a language model that can start payments on its own, within the rules set for it.
- MCP. Model Context Protocol, an open protocol for connecting AI agents to tools and data (introduction).
What Nouron Pass does with this
Nouron Pass is designed as an API and an MCP server. The idea is that the rules (limit per payment, daily cap, allowed destinations, WhatsApp approval and pause), applied outside the agent, also work for payments like those of x402. We do not claim it already supports x402: it is one of the payment methods we are evaluating for the future.
Today we do not process real payments yet. If you want your agent to be among the first, reserve your spot.
Frequently asked questions
Is x402 a cryptocurrency?
No. x402 is an open payment standard, a protocol on top of HTTP. The payments it describes are crypto-native, but the standard itself is not a currency or a token.
Does the x402 standard have fees?
According to its documentation, the standard itself does not include fees. Still, the service that charges, the network used and the provider you choose may apply their own.
Who maintains x402?
It is open source under the Apache-2.0 license and maintained by the x402 Foundation, according to the official documentation.
Can an agent that pays with x402 spend without a limit?
x402 does not define how much an agent can spend. That ceiling comes from the rules you apply outside the agent: limit per payment, daily cap, allowed destinations and human approval.
Does Nouron Pass already support x402?
No. It is one of the payment methods we are evaluating for the future, and for now it is part of the design, not an available product.
Put your agent to work with rules
Reserve your spot and we will write to you when your access opens.