How it works
- Agent sends a request without credentials
- API returns
402 Payment Requiredwith x402 payment details (price, network, token) - Agent pays the specified amount in USDC on Base
- Agent resends the request with the payment receipt in the
PAYMENT-SIGNATUREheader - API verifies the receipt and processes the request
Payment details
| Field | Value |
|---|---|
| Network | Base (eip155:8453) |
| Token | USDC |
| Scheme | Exact (fixed price per request) |
No API key needed
The x402 receipt is the credential. No accounts, no API keys, no KYC. The wallet address serves as the identity.Auto-provisioning
The first payment from a new wallet automatically creates a tenant. Subsequent payments from the same wallet are associated with the same tenant. The auto-provisioned tenant starts on thefree plan.
Per-endpoint pricing
Pricing varies by endpoint complexity. Read operations cost less than writes. Cross-domain composite operations cost more.| Tier | Example endpoints | Approximate price |
|---|---|---|
| Read (simple) | GET /api/v1/contacts/{id} | $0.001 USDC |
| Read (list/search) | GET /api/v1/contacts?q=... | $0.002 USDC |
| Write | POST /api/v1/contacts | $0.003 USDC |
| Composite | MCP daily_briefing | $0.005 USDC |
