Agent payments in 2026: x402 vs MPP — and why we built both

In the last 30 days, two payment protocols for AI agents shipped to production. They solve the same problem — letting autonomous agents pay for data and services — but they reach completely different buyer populations.

One of them will reach your agent depending on how its wallet was provisioned. Neither is going away.

The two rails

x402 is the HTTP 402 payment standard pioneered by Coinbase and a16z. When an agent hits a paywalled endpoint, the server returns:

HTTP/1.1 402 Payment Required
X-Payment-Response: {"price": "0.001", "currency": "USDC", "network": "base"}
WWW-Authenticate: x402 realm="clawmerchants.com"

The agent sends payment as a transaction on Base L2 (USDC), then retries the request with an X-PAYMENT header containing the transaction hash. The server verifies on-chain and delivers.

x402 agents are crypto-native. They have Base wallets, they understand calldata, and they are already probing x402 endpoints in production.

MPP (Machine Payments Protocol) was launched in March 2026 by Stripe and Tempo (Paradigm). When an agent hits a paywalled MPP endpoint:

HTTP/1.1 402 Payment Required
WWW-Authenticate: Payment realm="clawmerchants.com", challenge="..."

The agent responds with:

Authorization: Payment <encoded_session>

MPP agents have Stripe/Tempo-provisioned sessions. This is the enterprise path — credit cards, fiat, no crypto infrastructure required.

These are not competing standards. They are different distribution channels.

Live example: DeFi yields at $0.001/call

Here is a real endpoint that supports both:

# Probe the endpoint
curl -I https://clawmerchants.com/v1/data/defi-yields-live

# 402 response includes both protocols:
# WWW-Authenticate: Payment realm="clawmerchants.com"
# payment_info: {"price_usdc": 0.001, "protocols": ["x402", "mpp"]}

The current top pools (live right now):

{
  "preview": [
    { "protocol": "morpho-v1", "chain": "Ethereum", "symbol": "ALPHAUSDCENHANCEDV2", "apy": 19.99, "tvlUsd": 830842 },
    { "protocol": "uniswap-v3", "chain": "Base", "symbol": "USDC-LMTS", "apy": 19.53, "tvlUsd": 322821 },
    { "protocol": "uniswap-v3", "chain": "Optimism", "symbol": "WETH-WBTC", "apy": 19.49, "tvlUsd": 155916 }
  ],
  "total_pools": 50
}

An agent doing yield optimization calls this once per cycle at $0.001. At 1,000 calls/day, that is $1.00/day for live ranked yields across 50 pools. No subscription, no API key, no account.

Why we ship both

When we built ClawMerchants, the choice was not "which protocol." The choice was "which agents do we want to reach."

An agent with a Coinbase Base wallet cannot use MPP. An agent with a Stripe/Tempo session cannot use x402. These populations do not overlap much today.

By shipping both on day one of MPPs launch, any agent that discovers our OpenAPI spec can pay and call without friction. The WWW-Authenticate: Payment header signals MPP. The X-Payment-Response signals x402. Agents that understand one will ignore the other and proceed.

The implementation cost was one middleware layer and a second verification path. The reach is double.

How agent discovery works

Both protocols depend on the same discovery mechanism: the OpenAPI spec.

Our spec at clawmerchants.com/openapi.json lists 45 routes with inline payment metadata. MPP-compatible crawlers (including mppscan.com) index this automatically.

For x402-native agents, the 402 body includes a how_to_buy URL, current price, and protocol list — everything an agent needs to evaluate and pay without human involvement.

The pattern:

1. Agent discovers endpoint (OpenAPI, mppscan, x402 catalog)
2. Agent probes endpoint, receives 402 with price + protocol
3. Agent evaluates: "Is $0.001 worth this data for my current task?"
4. Agent pays via whichever protocol it supports
5. Data delivered, task continues

No forms, no OAuth, no API keys. The 402 is the contract.

What we learned

Three weeks of production data with real agent probes:

• 1,350+ 402 responses served
• Protocol discovery works — agents are probing before paying
• Conversion is the unsolved problem — probe → payment requires agents with funded sessions/wallets

The bottleneck is not UX or pricing. It is that most AI agents today do not have funded payment credentials. That changes as Coinbase, Stripe, and Visa push wallet infrastructure to developers — but it is not solved yet.

For builders launching agent-payable APIs now: ship both protocols, price at $0.001–$0.01/call, and optimize for discovery. The funded agents are out there. Make yourself findable.

---

Try it: probe https://clawmerchants.com/v1/data/defi-yields-live — the 402 body has the full price and protocol list.

Discover more: clawmerchants.com/openapi.json — 45 live data endpoints, all dual-protocol.

Inquiries: [e-mail]