Pay-per-request money for software.
x402 revives the long-dormant HTTP "402 Payment Required" status code as a real payment standard. Payouts.com implements x402 using USDC on Base/Ethereum L2, with auto-provisioned Coinbase wallets for agents — so an agent can pay for a resource the moment a server asks for payment.
0
calls metered
today
today
x402
What x402 provides
An HTTP-native payment standard for software: a server responds 402 with a payment offer, the agent pays in USDC and retries. Wallets are auto-provisioned, and a preflight step lets an agent probe a resource for its terms before paying.
HTTP-native payments
A server responds to a request with HTTP 402 and a payment offer. The agent inspects the offer, pays, and retries the request — no checkout page and no human in the loop.
Live request402
GET/v1/quote402
Payment offer0.10 USDC
pay-to 0xA1c4…d4f2 · Base
Inspect offer···
Pay 0.10 USDC···
Retry request···
Requests settled92,400
USDC on Base/Ethereum L2
Settlement runs in USDC on Base/Ethereum L2 for fast, low-cost machine payments — the right economics for pay-per-request and micropayments between software.
USDC settlement · PreviewRouting
Amount1,000.00 USDC···
Network fee~$0.001···
Finality~2s···
Settled in USDC$1,284,000
Auto-provisioned wallets
Every agent gets a Coinbase (CDP) wallet automatically — no manual setup. A preflight step probes a resource for its payment offer, then pays it programmatically.
Provisioning · PreviewGenerating
Ready
Balance$0.00
- Generate key pending
- Fund wallet pending
- Probe & pay offer pending
Wallets provisioned6,120
Reference
The complete API reference
Every endpoint, schema, and example — including the x402 preflight and pay calls — generated straight from our OpenAPI spec. Search it, expand any operation, and copy ready-to-run requests.
SDKs
Wire x402 into your agent stack.
Probe a resource for its 402 offer, pay in USDC, and retry — in a few lines of code, from any SDK.
TypeScript & Python SDKs
Call x402 from typed SDKs.
npm i @payouts/sdk or pip install payouts — preflight a resource, pay its 402 offer in USDC, and retry the request, all in a few lines.
SDK quickstart
index.tsmain.py
import { Payouts } from '@payouts/sdk'
const px = new Payouts(API_KEY)
const po = await px.payouts.create({
amount: 18420, currency: 'usd',
destination: 'acct_9Kd2Xa',
})
// → po.status === 'queued'
›
Weekly downloads600,000
Webhooks & MCP server
Stream x402 settlement events — signed and retried — and point Claude, Cursor, or your own AI agent at mcp.payouts.com to pay 402 offers as a tool call.
Event stream
mcp.payouts.comSSE · HMAC
payout.createdsigned
payout.settledsigned
transfer.completedsigned
refund.createdsigned
balance.updatedsigned
payout.failedsigned
Events delivered1,280,000
Sandbox parity & CLI
Sandbox keys return real payload shapes with test USDC. Simulate a 402 challenge, pay it, and inspect settlement. The
payouts CLI tails events live and bootstraps fixtures in one command.
Sandbox CLI
$
Sandbox requests92,400
Why x402
Why HTTP-native payments matter for agents
For software, the cleanest place to ask for payment is the moment a resource is requested — and that's exactly what the HTTP 402 status code was reserved for. With x402, a server responds to a request with a 402 and a payment offer; the agent inspects the offer, pays, and retries, all without a human in the loop or a checkout page. Payouts.com settles these payments in USDC on Base/Ethereum L2 for fast, low-cost transfers, and provisions a Coinbase wallet for the agent automatically so there's no manual setup. A preflight step lets an agent probe a resource for its payment terms before committing, making machine-to-machine commerce as routine as an API call.
Platform status
All systems operational
Uptime99.997%
p50 latency78ms
p99 latency412ms
Requests / sec · last 60s
- REST APIOperational
- DashboardOperational
- MCP serverOperational
- WebhooksOperational
- ACH · RTP · SEPAOperational
FAQ
Frequently asked questions
Everything you need to know about x402, the HTTP 402 payment standard, USDC settlement, and auto-provisioned agent wallets.
Still have questions?
What is x402?
A payment protocol built on the HTTP 402 status code, letting a server request payment for a resource and an agent pay it inline.
What currency and chain does it use?
USDC on Base/Ethereum L2, with auto-provisioned agent wallets.
Does x402 need a human to approve each payment?
No. The agent reads the server's 402 payment offer, pays, and retries automatically, within the limits you've set.
How does an agent get a wallet for x402?
A Coinbase wallet is auto-provisioned for the agent; settlement is in USDC on Base/Ethereum L2.
Let your agents pay.
Per request, in USDC.
Give your software the HTTP 402 payment standard: probe a resource, pay its offer, and retry — settled in USDC on Base/Ethereum L2 from an auto-provisioned agent wallet.