Executive Summary

In May 2025, Coinbase dusted off a status code that had sat unused for three decades. HTTP 402 — "Payment Required." Left in the original HTTP spec as a placeholder for a future paid internet, it was forgotten the moment credit cards took over. Now it's back — as the autonomous payment standard for AI agents.

x402 works simply: a server responds to an API request with 402; the client (an agent) automatically sends USDC and gains access. No account creation, no API key management, no human in the loop. V2 launched in December 2025. On April 2, 2026, x402 joined the Linux Foundation with Google, AWS, Microsoft, Stripe, Visa, Mastercard, KakaoPay, and 20+ others as founding members.

This post covers how x402 actually works, which services are using it, whether it works in Korea, and what it changes for data businesses.

HTTP status codes like 404 (Not Found) and 500 (Internal Server Error) are part of everyday internet life. But 402 is different. When HTTP was designed in 1991, its authors reserved this code with the expectation that a paid internet would eventually arrive. It never did — credit cards and subscription models took over, and 402 gathered dust for 30 years.

Coinbase recognized that this code's moment had finally come. The dominant actors on the internet are shifting from humans to AI agents. Agents don't create accounts. They don't go through KYC. They don't enter credit card numbers. But they do make HTTP requests — and if payment can be embedded in those requests, the way the internet handles money changes fundamentally.

1.1 The Problem with the Old Way

1.2 One Year of Growth

x402 follows the HTTP request-response cycle exactly. It's not a new communication protocol — it layers payment on top of existing HTTP.

2.1 The 5-Step Payment Flow

HTTP/1.1 402 Payment Required
Content-Type: application/json

{
  "accepts": [{
    "scheme": "exact",
    "network": "base-mainnet",
    "maxAmountRequired": "1000000",  // $1.00 USDC
    "asset": "0x833589...USDC",
    "payTo": "0xMerchantAddress"
  }],
  "description": "Weather data - 1 request"
}

2.2 One Line of Code to Add a Paywall

app.use(
  paymentMiddleware({
    "GET /weather": {
      accepts: [{ network: "base-mainnet", asset: "USDC", maxAmount: "1.00" }],
      description: "Weather data per request"
    },
    "GET /analytics": {
      accepts: [{ network: "base-mainnet", asset: "USDC", maxAmount: "0.10" }],
      description: "Analytics query"
    }
  })
);

2.3 What's New in V2

• • Wallet-based sessions: Pay once, and the same agent maintains access without re-paying every call
• • Dynamic payTo routing: Recipient and amount determined per-request — perfect for marketplaces and multi-tenant APIs
• • Multi-chain by default: Base, Solana, Polygon, and other L2s without custom code
• • Legacy rail compatibility: ACH, SEPA, and card payments via the same interface (deferred payment scheme)
• • Plugin-driven SDK: Add new chains and payment methods without touching the core spec

The most dramatic x402 demonstration comes from OpenMind's robot dog "Bits." When its battery ran low, Bits autonomously located the nearest charging station, plugged itself in, and paid for electricity in USDC — without any human intervention. HTTP request → 402 response → USDC transfer → charging begins. This is the agent economy, made tangible.

3.1 Key Services in the Ecosystem

3.2 MCP + x402 — Tools with Price Tags

The combination of Model Context Protocol (MCP) and x402 is particularly noteworthy. Individual tools on an MCP server can now carry explicit price tags that AI agents pay automatically.

// MCP server: mix free and paid tools
this.server.paidTool(
  "advanced-analysis",
  "Deep data analysis with proprietary models",
  0.05,  // $0.05 per call
  { dataset: z.string() },
  {},
  async ({ dataset }) => { /* analysis logic */ }
);

When an agent calls a paid tool, the MCP server responds with 402. The agent automatically pays and retries. Whether to require human confirmation is a configuration option.

x402's impact on data businesses goes beyond payment convenience. It's a lever for redesigning the business model itself.

4.1 From Subscriptions to Pay-Per-Query

Most data APIs today run on monthly subscriptions. Heavy use costs less per query, but light use means waste. x402 enables true pay-per-query — pricing each query, each analysis, each dataset exactly.

4.2 What Changes for Data Marketplaces

• • Dataset access gates — protect datasets behind x402 endpoints; agents buy exactly what they need
• • Real-time data streams — sell financial ticks and sensor data per event or per second
• • AI model inference — sell proprietary model outputs as paid API calls
• • Data quality validation — services like DataClinic auto-inserted into agent pipelines as paid quality gates

4.3 Agents Autonomously Purchasing Data Quality

Imagine a manufacturer's AI agent querying a data quality diagnostic API before running a defect prediction model. It sends a request; gets a 402; pays $0.30; receives a diagnostic report. If quality falls below threshold, it automatically calls a data cleaning API and pays again. Data pipeline quality gating, fully automated — no human required.

Bottom line: Technically usable today. Regulatory environment makes 2026 a pivotal year.

5.1 KakaoPay — A Linux Foundation Founding Member

KakaoPay appeared on the list of founding members when x402 joined the Linux Foundation on April 2, 2026 — alongside Visa, Mastercard, American Express, Google, AWS, and Stripe. This isn't ceremonial. It signals that KakaoPay has publicly committed to exploring x402-based agent payment integration into its platform.

5.2 The KRW Stablecoin Synergy

• • Visa publicly called Korea "the optimal country for stablecoin experimentation" (April 2026)
• • KB, Shinhan, Hana, and Toss are all developing KRW-pegged stablecoins
• • Korea's Digital Asset Basic Act is being legislated — KRW stablecoin issuance requirements being codified
• • x402 V2's plugin-driven SDK means adding a KRW facilitator requires no core spec changes

x402 creates a concrete business opportunity for DataClinic, Pebblous's core service.

6.1 The DataClinic MCP + x402 Scenario

DataClinic already has the infrastructure for dataset diagnostics and quality evaluation. Exposing it as an MCP server and monetizing it via x402 is a clear path forward.

6.2 What to Explore Now

• • Open a Coinbase CDP developer account → test x402's free tier (1,000 transactions/month)
• • PoC: add x402 middleware to a DataClinic API endpoint — one line of Node.js code
• • Monitor KakaoPay's x402 roadmap — integrate their facilitator when KRW payments go live
• • Deploy a lightweight DataClinic API on Cloudflare Workers → global x402 pay-per-query access point