Key takeaways:
-
x402 enables pay-per-use functionality on the internet.
-
The current momentum is infrastructure-led, driven by Coinbase and Cloudflare.
-
PING was a catalyst, but the real story is protocol adoption, not the token.
-
You can test it quickly by spinning up an endpoint and verifying the 402 → pay → grant flow.
X402 is a straightforward way to enable pay-per-use on the internet. When you access a paid application programming interface (API) or file, the server responds with the web’s built-in “402 Payment Required” message, specifying the price — often just a few cents in USDC (USDC) — and where to send the payment.
You send the onchain payment from your wallet, repeat the request, and the server delivers the result. There are no accounts, passwords, API keys or monthly plans — just a one-time payment linked to that specific request.
The “second wave” of x402
The idea isn’t new. The 402 status code has existed in HTTP for years, but it lacked a practical blueprint until 2025, when Coinbase packaged a clear protocol around it (“x402”). The company published documentation and code and offered a managed gateway for developers. Soon after, Cloudflare partnered with Coinbase to co-launch the x402 Foundation initiative, formalizing the standard and bringing support to mainstream developer tools.
You may have first heard about x402 when a token called PING drew attention to it. The token buzz faded, but the protocol endured because it solves a common problem: charging per API call, per AI inference or per download without requiring users to create accounts.
That utility, combined with new tooling for AI agents that can pay automatically, is driving a second wave focused on real usage rather than price charts.
Did you know? X402 is becoming the default way for AI agents to pay for things on their own. Cloudflare is adding native x402 support to its Agents SDK and MCP servers. Coinbase’s new Payments MCP allows popular large language models to hold a wallet and complete requests without API keys.
What is PING, who’s behind it, and how does it relate to x402?
PING is a memecoin on Base (Coinbase’s layer 2). It was the first public token mint executed through an x402 flow, which is why it grabbed headlines. Early buyers didn’t sign up on a website; they accessed a uniform resource locator (URL), received a “402 Payment Required” message, paid a small amount in USDC onchain, retried the request and received PING. Think of it as a live demo of x402’s pay-per-request model applied to minting.
The token was launched by the X account Ping.observer. Public coverage and listings consistently attribute PING to this account. There is no official team page or white paper beyond that and no credible disclosures of VC backing specific to the PING token itself.
X402 provided the infrastructure, while PING served as its first large-scale test case. The token’s pay-to-mint mechanic stress-tested the protocol and spotlighted x402’s core principle: charging a tiny onchain fee per request. That includes API calls, AI inferences, file downloads or, in this case, a mint, all without requiring accounts or API keys.
After the initial spike and retrace, the lasting impact was not the token price but the influx of developers and endpoints experimenting with x402.
Did you know? PING reached an all-time high of around $0.0776 on Oct. 25, 2025, before pulling back in the days that followed.
How to try x402 (developer quick start)
1) Get the gist
X402 is a simple handshake. You call a paid URL and the server replies with “402 Payment Required” and the price in USDC. You send the onchain payment, then call the URL again with the payment proof to get the result. That’s it.
2) Choose your setup
-
Managed: Use Coinbase’s hosted x402 gateway with dashboards and built-in Know Your Transaction (KYT) checks. It’s ideal for a quick proof of concept.
-
Do it yourself (DIY)/spec: Clone the open-source x402 reference implementation and run a minimal seller and buyer locally if you want full control.
3) Expose one paid endpoint
Pick any route (for example, “/inference”). When someone accesses it without paying, return a “402” response along with the payment details, including the amount, asset (USDC), destination address and expiry. If you can trigger that response using “curl,” you’re speaking x402 correctly.
4) Complete one paid request
Use the sample client or the managed gateway to detect the “402,” make the onchain payment, and then retry the request. Access should update automatically once the payment is confirmed, with no accounts, API keys or OAuth required.
5) Optional: Test with an AI agent
If you work with agents, spin up the model context protocol (MCP) example. The interceptor will detect the “402,” make the payment from the agent’s wallet and reissue the request automatically. It’s a quick way to confirm agent-to-endpoint flows.
Top tip: Start on a testnet as outlined in the quickstart….
cointelegraph.com