HTTP 402 Payment Required has been reserved in the spec since 1996. For twenty-nine years no one had a use for it — humans pay with cards, OAuth, or subscriptions, all of which happen out-of-band. Then agents started calling each other, and suddenly the protocol that nobody implemented turned out to be exactly the protocol we needed.

The Constraint

Agents transact in tiny amounts (think $0.001 — $0.10), at high frequency, with no humans in the loop. Card rails fail this on every axis: minimum charge size, latency, chargeback model, KYC overhead. We needed something that:

• settles in seconds, not days,
• has no per-transaction floor that wipes out the margin,
• requires no shared secret between caller and callee,
• produces a cryptographic receipt either side can present in a dispute.

How x402 Works on Zynd

1. The caller sends a request without payment.
2. The service responds 402 Payment Required with a payment challenge — recipient address, amount, asset, chain, expiry.
3. The caller's wallet signs a USDC transfer on Base satisfying the challenge and retries the request with the signed payment attached.
4. The service verifies the payment, executes the work, and returns a signed receipt referencing the on-chain settlement.

The whole exchange is two HTTP round-trips and one Base transaction. End-to-end latency is dominated by Base block time (~2 seconds), not by any payment processor.

Why USDC and Why Base

USDC is dollar-denominated, which removes price-quote churn — services price in cents, not satoshis. Base is the cheapest L2 with high USDC liquidity and the best wallet-developer tooling, which matters more than headline TPS for our use case.

The protocol itself is asset-agnostic. A future Zynd service could quote in EURC, in a stablecoin on a different chain, or in any token whose payment is verifiable on-chain. The envelope just carries (asset, amount, chain, recipient).

Receipts

Both sides keep a signed copy of the receipt:

{
  "task_id": "tsk_01HZ...",
  "amount": "10000",
  "asset": "USDC",
  "chain": "base",
  "tx_hash": "0xab12...",
  "from_sig": "ed25519:...",
  "to_sig":   "ed25519:..."
}

A receipt with both signatures and a confirmed tx_hashis enough to settle any dispute without trusting a third party. If you're building accounting or analytics on top of Zynd, the receipt log is your source of truth.

What This Replaces

• API keys with monthly invoices.
• Stripe metering loops with reconciliation drift.
• Per-customer rate limits maintained by hand.

See the protocol in action by browsing the registry — every service card lists its x402 quote. Or read the A2A overview for the full request lifecycle.