Understanding x402

Many digital services—APIs, data feeds, AI tools, and premium content—need a simple way to charge per use. Traditional payment systems rely on accounts, subscriptions, logins, and credit cards, which create unnecessary friction.

x402 is an open web standard that enables pay-as-you-go access directly over HTTP. Instead of forcing people or systems to sign up, x402 lets them pay only when they need access.

x402 is built around a familiar HTTP status code: 402 Payment Required

When a client requests something that costs money, the server returns a 402 response containing payment instructions. After the payment is made, the client retries the request and gets access—no accounts, no forms, no registration.

Where x402 Can Be Used

Monetizing APIs - Charge per API call without creating an account system or subscription tiers.

Selling Digital Content - Reports, files, datasets, and other resources can be paid for on demand.

Allowing AI Agents to Pay Automatically - Bots and automated systems can pay for tools and data without manual steps.

Metering Micro-Services - Small internal or external services can bill per request with minimal overhead.

How x402 Works

1. The client requests a resource

GET /weather/today

2. The server responds with 402 Payment Required, including cost and payment details:

{
  "status": 402,
  "payment": {
    "amount": "0.10",
    "currency": "USDC",
    "instructions_url": "https://example.com/pay"
  }
}

3. The client sends payment - This usually involves a wallet or facilitator handling the transfer.

4. The client retries the request with proof of payment

GET /weather/today
X-402-Payment: <payment-proof>

5. The server verifies payment and returns the result

{
  "temperature": "72F",
  "conditions": "Clear"
}

The flow requires no personal information—only a valid payment.

Advantages of x402

Simple monetization - Charge per use without building account systems, billing dashboards, or credit card workflows.

Low friction - Users (or AI agents) pay instantly without logging in or storing sensitive data.

Supports micropayments - Charge fractions of a cent efficiently—something traditional processors can't do.

Works for humans and machines - Whether it's a person fetching a premium file or an AI agent calling an API, the payment process is the same.

Open and interoperable - Any service or client can adopt x402. It isn't tied to a single company or platform.

A Simple Before-and-After Example

Traditional paid access

To get paid access to an API or digital file, you typically need:

• Accounts
• Logins
• Saved payment methods
• Billing portals
• Fraud checks
• Email confirmation
• Subscription handling

With x402

1. Request resource
2. Receive a 402 with payment instructions
3. Pay
4. Retry and receive the resource

The entire flow is minimal and automated.

---

x402 makes it possible to monetize digital content and APIs using a simple, account-less, pay-as-you-go system built on standard HTTP. It reduces friction, supports micro-transactions, and works equally well for human users and autonomous agents.