Since 1997 the rules of the web have provided a status code of its own for payment: 402, “Payment Required”. It was reserved for future use and remained largely unused for almost 30 years. With x402 it is having a renaissance: a piece of software requests data from a provider, is quoted a price of a few cents instead of receiving an answer, pays and gets the data, without having an account there.
What this is about
Software increasingly calls up services on the web by itself and is expected to pay for them by itself too. An AI agent, that is, software acting on behalf of a person or a company, may request data, computing power or content a hundred times a day, often for a few cents. An account with every provider is too cumbersome for that, and at such amounts the fixed fee of a card payment eats up the price.
This concerns the API economy, in which companies sell data and functions through APIs, and every service that is called up on the web one request at a time. x402 is one way to solve this. NemosGo, which runs this site, pursues the same goal by a different route. This article explains both and says when each one fits.
x402 at a glance
x402 is an open protocol. It defines how a payment becomes part of a request on the web. The official site is x402.org.
| FEATURE | X402 |
|---|---|
| What it governs | payment for a single request over HTTP, without a customer account at the provider |
| Developed by | Coinbase, presented on 6 May 2025; a second version for several blockchains has existed since December 2025 |
| Backed by | the x402 Foundation at the Linux Foundation, operating since 14 July 2026; 40 members at the start, including Visa, Mastercard, American Express, Stripe, Google, AWS, Adyen, Cloudflare, Shopify and Fiserv, more than 50 today |
| Paid in | stablecoins, that is, digital coins whose value is pegged to a currency, mostly USDC, pegged to the US dollar; settled on a blockchain such as Base, a network from Coinbase built on Ethereum, Solana or Polygon |
| What it costs | The protocol itself is free, and booking on the blockchain costs fractions of a cent per payment. On top of that come the charges of the other parties involved, such as the settlement service or the exchange that converts euros into stablecoins and back. With Coinbase’s service, 1,000 transactions a month are free, after that each costs 0.001 US dollars. |
| Spending limits | Since August 2026 the software libraries have capped each payment at one US dollar by default, and the spending controls are being extended. Coinbase also offers buyers limits per payment and per period, for example 24 hours. |
How a payment works
A payment with x402 is a second request, this time with a signature. It takes five steps:
- The buyer’s software requests a resource from the provider, such as a data set.
- The provider replies with status code 402 and states what it accepts: amount, stablecoin, blockchain and recipient.
- The software uses its wallet key to sign a payment authorisation for this amount and sends the same request again, this time with the signature.
- The provider has the payment checked and executed on the blockchain, usually by a service the protocol calls a facilitator. It can also do this itself.
- The provider delivers the resource together with a confirmation containing the transaction ID.
Besides the fixed price, x402 offers further variants. With billing by usage, the buyer authorises a maximum amount and the provider charges only what was actually used. With batch settlement, many payments are collected and booked together on the blockchain. And with escrow payments, the money is released only after delivery, or refunded otherwise.
Three roles in the protocol, more in practice
The protocol knows three roles: buyer, provider and facilitator. For money to actually flow, further parties are needed that the protocol assumes but does not govern.
| ROLE | WHAT IT DOES | WHO FILLS IT, FOR EXAMPLE |
|---|---|---|
| RoleBuyer | What it doesholds stablecoins in a wallet and signs each payment | Who fills it, for examplean agent’s software |
| RoleProvider | What it doesstates the price and recipient address and delivers after payment | Who fills it, for examplethe operator of the API |
| RoleFacilitator | What it doesverifies the payment and executes it on the blockchain without holding money; at Coinbase this includes screening against sanctions lists | Who fills it, for exampleCoinbase and other services |
| RoleNetwork | What it doesrecords the transfer | Who fills it, for exampleblockchains such as Base, built by Coinbase, or Solana |
| RoleWallet | What it doesholds the keys of buyer and provider | Who fills it, for examplethe owners themselves or services such as Coinbase |
| RoleIssuer | What it doesissues the stablecoin and redeems it for dollars | Who fills it, for exampleCircle for USDC |
| RoleExchange | What it doesswaps euros into stablecoins and back | Who fills it, for examplecrypto exchanges and payment services |
Two things stand out. One company can fill several roles at once: Coinbase developed x402, runs a facilitator, built the Base network, offers wallets and is itself an exchange. And whoever sends the agent out does not appear in the protocol at all. They fill the wallet and set up the software.
What settling on a blockchain involves
With x402, every payment is booked directly on a blockchain. That has tangible consequences for buyers and providers:
- How long a payment takes until it is final depends on the network. On Base, the provider sees it within seconds; it is final after around 20 minutes, once it has been recorded on Ethereum. Payment is possible around the clock and worldwide.
- Booking on the blockchain costs fractions of a cent. On top of that come the charges of service providers and exchanges.
- The buyer needs no account with the provider and gives it no personal data. The payment is still visible: on the blockchain, under the address of the buyer’s wallet rather than a name.
- A payment, once executed, is irrevocable; there are no chargebacks as with cards. Refunds are made by a new transfer back or through the escrow variant.
- As proof, both hold the transaction ID, which can be looked up on the blockchain.
In return, this route requires the tools of the crypto world. The buyer needs a wallet with stablecoins. The provider receives stablecoins; if it keeps its books in euros, it exchanges them or has a service do so. Anyone at home in the crypto world already has these tools.
Where x402 is used
x402 is designed for selling APIs, for purchases by agents and for paywalled content. Some examples:
- CoinGecko, a provider of cryptocurrency market data, sells requests via x402 for 0.01 US dollars.
- Since February 2026, Stripe has enabled companies, in a preview, to bill agents per request.
- Since June 2026, the AWS Web Application Firewall can bill bots and agents for requests via x402.
- In Europe, AllUnity, a licensed e-money institution, offers x402 with stablecoins in euros and other currencies, with payout to a bank account.
What NemosGo does differently
NemosGo is built in a fundamentally different way. Some goals and functions are the same: software should be able to pay per request, without a subscription and without an account with every provider, and small amounts should be worthwhile too. The route there is a different one:
- No blockchain, in euros. Buyers and providers need neither stablecoins nor a blockchain. NemosGo holds no money.
- Within existing APIs. The provider keeps its API and decides what a function costs. It is offered where agents already work, for example as a connector in an AI assistant.
- Verified providers. Providers are checked before their first sale; how this works is described below under the MACP Wizard.
- With approval. Before the purchase, a person confirms the individual purchase or gives an agent a budget in advance, with an amount, a purpose and a period. The limit is set by whoever sends the agent out.
- One transaction through to the receipt. Every purchase runs from approval through delivery to invoice and receipt.
- The provider decides. Price, terms and brand stay with the provider. The contract is made between provider and buyer, with no platform in between.
- Auctions too. If the price is not fixed in advance, NemosGo determines it by auction, with rising or falling prices.
How a request is paid for with NemosGo
With NemosGo, the M-Pay API Consumption Protocol, MACP for short, governs how software finds, pays for and calls a paid API. The protocol, the developer kit and the handbook are published on Codeberg under a free licence. A proxy sits between buyer and provider: it quotes the price, takes the payment and only then calls the provider’s function. It takes five steps:
- The buyer’s software asks the proxy which functions are available and what they cost.
- It obtains a quote for the call it wants, the invoice.
- It pays the invoice from its wallet, within what a person has approved, and receives an authorisation for exactly this one call.
- With this authorisation it calls the function. The proxy checks it and forwards the call to the provider’s API.
- Back come the result, proof of execution and the receipt.
The provider changes nothing in its API; it only sees the call to its own function. Quote, payment and execution are separate steps, cryptographically linked to one another: the authorisation is valid only for this invoice and this function, and the proof of execution belongs to exactly this authorisation. So the buyer holds an invoice before paying and proof afterwards. The flow is described in detail on the For developers page.
Providers join through the MACP Wizard, a web application that has been public since September 2026: after an application and a check of the company, they publish their API there with a price per function. More on this on the For sellers page.
When x402 fits and when NemosGo does
x402 is the natural connection for anyone who already buys and sells in the crypto world. Wallet and stablecoins are in place, payment works worldwide, and the protocol, network and settlement are looked after by the foundation and the service providers.
NemosGo fits companies and people who pay and keep their books in euros, who want to approve their agents’ purchases in advance or steer them with budgets, and who need an invoice and a receipt for every purchase. Price, terms and brand stay with the provider, under European law.
Conclusion
Status code 402 only says that payment is required, not how. That x402 uses stablecoins on a blockchain for this does not follow from the status code. It is a decision by Coinbase, which grew up as a crypto exchange. According to its developers, the second version is also meant to be able to include traditional payment routes such as the card networks.
That a status code from 1997 is being used almost thirty years later shows how seriously the industry takes payments by machines. Card networks, payment processors and cloud providers now stand behind x402. Whether one method prevails or several exist side by side, as cards, transfers and direct debits do today, remains open. For Europe, what is at stake is whether machines can pay in euros without the detour through stablecoins, and whether the rules for this are written here or by the large platforms.
Sources
As of 9 November 2026. Figures and details checked against the originals on 5, 7 and 9 November 2026.
| SOURCE | DATE |
|---|---|
| IETF, RFC 2068, HTTP/1.1, status code 402rfc-editor.org/rfc/rfc2068 | January 1997 |
| x402, official sitex402.org | no date |
| Coinbase, launch of x402coinbase.com/developer-platform/discover/launches/x402 | 6 May 2025 |
| The Block, second version of x402theblock.co/amp/post/382284/coinbase-incubated-x402-payments-protocol-built-for-ais-rolls-out-v2 | 11 Dec 2025 |
| Linux Foundation, operational launch, 40 memberslinuxfoundation.org/press/linux-foundation-announces-operational-launch-of-x402-foundation-to-standardize-internet-native-payments-for-ai-agents-and-applications | 14 Jul 2026 |
| Linux Foundation, executive director of the x402 Foundation, more than 50 memberslinuxfoundation.org/press/linux-foundation-appoints-michael-hursta-as-executive-director-of-the-x402-foundation | 1 Oct 2026 |
| Coinbase Developer Platform, facilitator and pricingdocs.cdp.coinbase.com/x402/seller/facilitator | no date |
| The Hacker News, audit by V12thehackernews.com/2026/10/critical-x402-sdk-flaw-could-let.html | 23 Oct 2026 |
| x402 Foundation, changelog of the software librarygithub.com/x402-foundation/x402/blob/main/typescript/packages/core/CHANGELOG.md | as of 7 Nov 2026 |
| Coinbase Developer Platform, spending limits for buyersdocs.cdp.coinbase.com/x402/buyer/client-configuration | no date |
| x402, client and server documentationdocs.x402.org/core-concepts/client-server | undated |
| x402, payment schemesdocs.x402.org/schemes/overview | no date |
| x402, facilitator documentationdocs.x402.org/core-concepts/facilitator | undated |
| x402, wallet documentationdocs.x402.org/core-concepts/wallet | undated |
| Coinbase Developer Platform, overview of x402 and walletsdocs.cdp.coinbase.com/x402/welcome | undated |
| Base, built by Coinbasebase.org | undated |
| Base, transaction finalitydocs.base.org/specifications/transactions/transaction-finality | no date |
| Circle, USDCcircle.com/usdc | as of 2 Nov 2026 |
| x402, FAQdocs.x402.org/faq | no date |
| CoinGecko, about uscoingecko.com/en/about | no date |
| The Block, Stripe and CoinGeckotheblock.co/post/389352/stripe-adds-x402-integration-usdc-agent-payments | 11 Feb 2026 |
| AWS, Web Application Firewall with x402aws.amazon.com/about-aws/whats-new/2026/06/aws-waf-ai-traffic-monetization/ | 15 Jun 2026 |
| The Block, AllUnitytheblock.co/news/markets/2026-05-20-allunity-plans-swedish-krona-stablecoin-launches-agentic-payments-infrastructure-402027 | 20 May 2026 |
| AllUnity, agentic paymentsallunity.com/product-docs/set-up-agentic-payments | no date |
| NemosGo, MACP Wizardmacp-wizard.digital-platform.io | no date |
Let us talk
Working on the same question, or see it differently? Write to us.