x402
⚠Review·Scanned 2/17/2026
x402 implements HTTP-native stablecoin payments (SDK and CLI) to handle 402 Payment Required flows for APIs and AI inference. It reads WALLET_PRIVATE_KEY, signs payments and sends payment proofs to network endpoints (e.g., https://mainnet.base.org, user-supplied URLs) and includes runnable commands like npx ts-node x402-fetch.ts and npx x402 pay.
from clawhub.ai·v3261ac5·17.1 KB·0 installs
Scanned from 1.0.0 at 3261ac5 · Transparency log ↗
$ vett add clawhub.ai/0xterrybit/x402Review findings below
x402 Payment Protocol
x402 enables instant stablecoin payments directly over HTTP using the 402 Payment Required status code. Perfect for AI agents paying for APIs, data, or compute on-demand.
Quick Start
Install SDK
npm install x402
# or
pnpm add x402
Environment Setup
# Store wallet private key securely
export WALLET_PRIVATE_KEY="0x..."
# Optional: specify network RPC
export BASE_RPC_URL="https://mainnet.base.org"
How x402 Works
- Request → Client calls a paid API
- 402 Response → Server returns payment details in
PAYMENT-REQUIREDheader - Pay & Retry → Client signs payment, retries with
PAYMENT-SIGNATUREheader - Access → Server verifies, settles, returns resource
Using x402 Client
TypeScript/Node.js
import { x402Client } from 'x402';
const client = x402Client({
privateKey: process.env.WALLET_PRIVATE_KEY,
network: 'base', // or 'ethereum', 'arbitrum', etc.
});
// Automatic 402 handling
const response = await client.fetch('https://api.example.com/paid-endpoint');
const data = await response.json();
With fetch wrapper
import { wrapFetch } from 'x402';
const fetch402 = wrapFetch(fetch, {
privateKey: process.env.WALLET_PRIVATE_KEY,
});
// Use like normal fetch - 402s handled automatically
const res = await fetch402('https://paid-api.com/data');
Manual Flow (curl)
Step 1: Discover payment requirements
curl -i https://api.example.com/paid-resource
# Returns 402 with PAYMENT-REQUIRED header (base64 JSON)
Step 2: Decode payment details
# The PAYMENT-REQUIRED header contains base64-encoded JSON:
# {
# "amount": "1000000", # 1 USDC (6 decimals)
# "currency": "USDC",
# "network": "base",
# "recipient": "0x...",
# "scheme": "exact"
# }
Step 3: Sign and pay
# Use x402 CLI or SDK to create payment signature
npx x402 pay \
--amount 1000000 \
--recipient 0x... \
--network base
Step 4: Retry with proof
curl -H "PAYMENT-SIGNATURE: <base64_payload>" \
https://api.example.com/paid-resource
Common Patterns
Pay for API calls
// Weather API that costs 0.001 USDC per call
const weather = await client.fetch('https://weather-api.x402.org/forecast?city=NYC');
Pay for AI inference
// LLM API with per-token pricing
const completion = await client.fetch('https://llm.example.com/v1/chat', {
method: 'POST',
body: JSON.stringify({ prompt: 'Hello' }),
});
Check balance before paying
import { getBalance } from 'x402';
const balance = await getBalance({
address: walletAddress,
network: 'base',
token: 'USDC',
});
if (balance < requiredAmount) {
console.log('Insufficient USDC balance');
}
Supported Networks
| Network | Chain ID | Status |
|---|---|---|
| Base | 8453 | ✅ Primary |
| Ethereum | 1 | ✅ Supported |
| Arbitrum | 42161 | ✅ Supported |
| Optimism | 10 | ✅ Supported |
| Polygon | 137 | ✅ Supported |
Payment Schemes
- exact: Pay fixed amount (e.g., $0.01 per API call)
- upto: Pay up to max based on usage (e.g., LLM tokens)
- subscription: Wallet-based access with sessions (V2)
Error Handling
try {
const res = await client.fetch(url);
} catch (err) {
if (err.code === 'INSUFFICIENT_BALANCE') {
// Need to fund wallet
} else if (err.code === 'PAYMENT_FAILED') {
// Transaction failed on-chain
} else if (err.code === 'INVALID_PAYMENT_REQUIREMENTS') {
// Server sent malformed 402 response
}
}
Security Notes
- Never expose private keys in logs or chat
- Use environment variables for wallet credentials
- Prefer
op runor similar for secret injection - Review payment amounts before confirming large transactions
V2 Features (Dec 2025)
- Wallet-based identity: Skip repaying on every call with sessions
- Auto-discovery: APIs expose payment metadata at
/.well-known/x402 - Multi-facilitator: Choose between payment processors
- CAIP standards: Universal chain/asset identifiers
Resources
- Spec: https://github.com/coinbase/x402
- Docs: https://docs.cdp.coinbase.com/x402
- Demo APIs: https://www.x402.org