x402 is an open, internet-native payment protocol built around HTTP status code 402 — "Payment Required" — a code reserved in the web's original design but never activated. Incubated by the Coinbase Development Platform team and now maintained as an open standard, x402 lets any API or web service require payment before serving a response. No accounts, no API keys, no subscriptions, no invoices. A client requests a resource, the server replies with a price, the client attaches a signed stablecoin payment to the retried request, and the content is delivered — all within the normal HTTP flow.
For the first time, payments become a native primitive of the web itself. Learn more about the standard at x402.org.
When agents transact thousands of times per hour, the settlement rails decide whether the economics work. XDC Network is built for exactly this profile:
AI agents are no longer just generating text. With modern tool use and context protocols, agents research, execute, and transact with minimal human supervision. They will pay for data feeds, fund their own compute, subscribe to services, and settle with other agents — continuously and autonomously.
This is the rise of agentic payments: a layer of the internet economy where machine-to-machine transactions represent a growing share of demand for digital services. Traditional payment rails — card networks, invoicing, subscription billing — were built for humans at human speed. They cannot underwrite an agent making a $0.001 payment every 400 milliseconds.
x402 on XDC gives that economy working rails: gasless USDC settlement, deterministic finality, and predictable sub-cent costs, on infrastructure already trusted for institutional finance.
The x402 standard is blockchain-agnostic and backed by a growing community of SDK builders, payment facilitators, and platform integrations. On XDC, builders are shipping x402-enabled API servers, AI payment agents, and developer tooling that make monetizing any endpoint as simple as adding a middleware. Because x402 rides on plain HTTP, it composes cleanly with MCP servers, agent frameworks, and existing web infrastructure — no protocol lock-in, no proprietary rails.
x402 on XDC is built into existing HTTP requests, with no additional communication required. There's no new protocol to adopt, no separate payment channel to open, no webhook to configure — the 402 status code and the payment header ride inside the same request/response cycle every API already speaks.
That means any HTTP client, server, or agent framework can add x402 support without re-architecting how it talks to the network. A request goes out, a 402 comes back if payment is due, a signed USDC payment gets attached on retry, and XDC settles it — all inside the HTTP calls that were already happening.
Getting paid for an API on XDC takes one line of middleware:
That's it. Add one line of code to require payment for each incoming request. If a request arrives without payment, the server responds with HTTP 402, prompting the client to pay and retry — settled on XDC in seconds, for a fraction of a cent.
Paying is just as simple on the client side:
How do I integrate x402?
Read the Quickstart for Sellersx402 works the same way whether you're serving an API or building the agent that calls it.
Here's how different builders get started:
XDCAI.tech is the reference implementation of agentic commerce on XDC Network — a payment, control, and settlement framework built around the open x402 standard. It gives autonomous agents a non-custodial smart wallet and a compliant, regulated framework for paying for APIs and digital services in USDC, without subscriptions, invoices, or credit cards.
Under the hood, XDCAI combines gasless USDC payments (via EIP-3009) with user-controlled on-chain spending limits, pay-per-call API transactions, and machine-readable transaction records for every request. It supports agent-to-agent and agent-to-business payments out of the box, and integrates directly with platforms like ChatGPT, Claude, Codex, and Cursor — so an agent running in any of those environments can discover a paid service and settle payment without leaving its workflow.
XDCAI.tech is built on the same rails as native USDC and Circle's CCTP V2 on XDC Network, both already live and supporting fast, ISO 20022-compliant messaging and low-cost cross-chain transfers. It's a practical example of what "x402 on XDC" looks like in production — not a demo, but working infrastructure for a future where millions of autonomous agents transact with one another.