Agent commerce

Every WAVE capability is payable by an autonomous agent over HTTP-402 (x402) and the Machine Payments Protocol (MPP). No account, no stored card, no human in the loop. Pay per call.

How it works

1. Discover. An agent reads a machine-readable manifest — /.well-known/x402, MPP discovery, OpenAPI, or a skill descriptor — to learn what's offered and how to pay.
2. Negotiate. The resource answers HTTP 402 Payment Required with the exact terms: scheme, network, amount, and where to send it.
3. Settle. The agent signs the payment authorization and retries the call with an x-payment header. Settlement runs on Base mainnet, with sanctions screening on the path.
4. Receive. The gateway verifies the payment on-chain and serves the resource. No polling, no webhook to wire up first.

WAVE Dispatch — WAVE's edge AI inference and routing service — publishes its live x402 terms as the public exemplar: every product on the gateway answers the same way.

The 402 challenge, live

A call with no payment attached gets a 402 back with the exact terms to satisfy:

curl -s -X POST https://api.wave.online/v1/render \
  -H "Content-Type: application/json" -d '{}'

{
  "x402Version": 1,
  "error": "payment required",
  "accepts": [{
    "scheme": "exact",
    "protocol": "x402",
    "network": "base",
    "maxAmountRequired": "600000",
    "resource": "/v1/render",
    "payTo": "0x13014b6e42d6cae7d82798c17244b003c431b68c",
    "asset": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
    "maxTimeoutSeconds": 60
  }],
  "next_action": { "type": "pay", "protocol": "x402" }
}

Sign the accepts[0] authorization, retry with the x-payment header, and the gateway serves the render. See MPP for the second machine-payment protocol the gateway accepts alongside x402.

Discovery surfaces

Built on the open x402 standard and MPP. An agent transacts the same way you use an API key: one credential, one contract, metered per call.