How x402 Works Here 🟡 Beta

x402 is an open payment protocol built on HTTP's long-dormant 402 Payment Required status. The flow:

 1. Agent calls scan_token (no payment)
 2. Server  → 402 + X-PAYMENT-ACCEPTS: {asset: USDC, network: base, amount: 0.002, recipient: 0x...}
 3. Agent signs payment payload, retries with X-PAYMENT header
 4. Server verifies via facilitator (x402-coffer), executes tool
 5. Response carries X-PAYMENT-RESPONSE (receipt) + result

Why x402 instead of API keys?

Concern	API keys	x402
Signup friction	Form + email + dashboard	None — wallet is the identity
Billing	Invoice cycle	Per-call, settled in seconds
Revocation surface	Key database = honeypot	Nothing stored
Machine-native	No	Yes — designed for agents

Supported networks

Base (primary) and Solana. Settlement asset: USDC. See x402-coffer for the facilitator we run.