Make payments invisible. Pay per API request.
Per-request payments for APIs & agents.
Adopt the x402 payment standard without building wallets or ledgers. Top up once with USDC; our SDK pays per call, retries when funds run out, and provides clear logs and spend limits.
curl -i https://api.yourservice.com/pro
HTTP/1.1 402 Payment Required
x-402: top-up @ https://flow402.com/pay?ref=abc123Workflow
How it works
Why Flow402
Adopt x402 without the heavy lifting
Replace brittle paywalls with per-request payments that work across agents and APIs— without dragging users on-chain every call.
Predictable UX
No wallet pop-ups or on-chain wait per call.
x402-native
Adopt x402 with minimal code: SDK + gateway.
Real logs
Usage logs, alerts, and spend caps (Supabase-ready).
Use cases
Built for agents, APIs, and creators
Developer preview
Drop-in snippets for Flow402 integration
Test x402/402 flows with a single curl call, then wire per-request credits into your client or agent runtime with a few lines of TypeScript.
Curl preview
curl -i https://api.yourservice.com/pro
HTTP/1.1 402 Payment Required
x-402: top-up @ https://flow402.com/pay?ref=abc123TypeScript fetch
const r = await fetch("/your/paid/endpoint");
if (r.status === 402) {
const payLink = r.headers.get("x-402");
// show UI to top-up via Flow402
}FAQ
Answers for operators
Is this on-chain every call?
No. Only top-ups and settlements are on-chain. Per-request debits are handled off-chain for speed and cost.
Why not just subscriptions?
Subscriptions don’t fit irregular, agent-driven workloads. We make per-request pricing simple.
What chains/assets first?
USDC on Base to start; more assets and networks later.
How do I get in?
Apply for beta. We’re onboarding small cohorts weekly.
Security?
Server-side secrets never hit the client. Settlements are on-chain and auditable.
Pricing?
Early users get founder-friendly pricing; public pricing at GA.