Make payments invisible

Make 402 invisible.

Pay-per-request credits for APIs & agents.

When balance hits zero, your API returns 402—Flow402 auto-tops-up in USDC and retries. You keep charging per call without on-chain friction.

HTTP 402 Examplex402

curl -i https://api.yourservice.com/pro
HTTP/1.1 402 Payment Required
x-402: top-up @ https://flow402.com/pay?ref=abc123

Workflow

How it works

User tops up once (e.g., $5–$10 USDC)

Each paid request debits credits off-chain instantly

If low balance, your API returns HTTP 402

Occasional on-chain settlement for clear accounting

Why Flow402

Replace brittle paywalls with credits that work across agents, APIs, and human flows—without pulling users on-chain every call.

No per-call on-chain friction.

Simple pay-links & gateway routes.

Supabase-ready tracking and auditability.

Use cases

AI Agents: call external tools and pay per use.

APIs: metered endpoints without subscriptions.

Creators: pay-to-unlock premium files & links.

Data Providers: charge for datasets & queries.

Developer preview

Test HTTP 402 flows with a single curl call, then wire 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=abc123

TypeScript 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

No. Only top-ups and settlements are on-chain; per-request debits are off-chain for speed and cost.

Subscriptions don’t fit irregular, agent-driven workloads. We support per-request pricing cleanly.

USDC on Base initially, with more assets/networks later.

Apply for beta. We’re onboarding small cohorts weekly.

Server-side secrets never hit the client. Settlements are on-chain and auditable.

Early users get founder-friendly pricing; we’ll publish public pricing at GA.

By applying, you agree to be contacted about Flow402.