x402 is how machines pay machines — but done wrong, it exposes your customers' spend patterns to anyone watching the chain. We install the privacy-preserving version: verified agent identity, no wallet-activity leaks, and an on-chain receipt for every settlement so finance can audit it. You never read the spec.
Before anything: is your endpoint payable by an agent, yes or no? We scan it with the same tooling behind our 747-host audit and hand you a one-page buyer-readiness report. If you go on to an install, the $99 comes off the setup fee.
Demo before you pay. Invoiced in USD (ACH, wire, or card) — or USDC if you prefer. Every package ships the privacy-preserving gate: agent identity checks, no spend-pattern leakage, settlement receipts.
$500 one-time, + $99/mo
.well-known/x402.json, OpenAPI price tags, CI test script, dashboard$499 per month
Let's talk one-time + monthly
One line about what your API does and the route you want paid. We reply with questions only if we must — usually same day.
Payment gate, discovery wiring, identity checks, test script. You watch a real agent pay your endpoint before you pay us.
USDC settles straight to your wallet with an on-chain receipt your finance team can pull anytime. The retainer keeps the rail alive as the spec evolves.
Yes. We invoice in USD — ACH, wire, or credit card — and provide a W-9. USDC payment is available if you prefer it, never required.
The minimum the protocol requires: payment amount, payee, and the settlement receipt. We never see your buyers' wallet histories, balances, or spending patterns — and our privacy wiring keeps their other activity on-chain from being linked to what they pay you.
Never. Settlement goes on-chain straight to your wallet. Our facilitator verifies and settles; the money never touches an account of ours.
Every paying agent is identity-checked via our Know-Your-Agent rail (ERC-8004 identity plus attestations) and credit-scored before they're allowed through. No anonymous scrapers. Suspicious agents get declined at the gate.
Every settlement produces an on-chain receipt — payer, payee, amount, timestamp, transaction hash. Exportable quarterly. Your auditors don't need to trust us; they read the chain.
Base L2 (eip155:8453), USDC, settled through Coinbase CDP. More networks as the spec adopts them.
No. x402 is three HTTP concerns: the 402 response, payment verification, and settlement. We integrate with whatever serves your route — Flask, Go, Rust, serverless, nginx in front of anything.
That's what the retainer is for. Protocol updates get applied within 14 days — which is exactly what didn't happen to the 80% of endpoints we found broken.
The concierge is done-for-you, but your engineers can verify our rail is real before the first call:
curl -s https://x402-agent-pay.com/facilitator/supported → {"chainId":"8453","maxUnitsRequired":...,"supports":["exact","base"]} curl -s -X POST -H 'Content-Type: application/json' -d '{}' \ https://x402-agent-pay.com/facilitator/verify → {"fault":"payer","invalidReason":"MALFORMED_PAYLOAD",...} ← a real, working verifier answers
[email protected] — a human answers, usually same day.