NexFlow by EasePay

Agent‑native metered billing
for any API

Drop‑in x402 payments, multi‑facilitator routing, and on‑chain verification so your agents can pay per call.

Verified0.001 USDCon Base • 2s ago
Verified0.05 USDCon Base • 5s ago
Verified0.002 USDCon Base • 12s ago

Multi‑facilitator cascade

Automatic failover through CDP, PayAI, OpenX402, and on‑chain.

Multi‑chain support

Base first, with Ethereum, Polygon, Arbitrum, and more chains.

Metered endpoints

Set price per call, per token, or per custom unit.

The payments brain your agents deserve

A complete pipeline from agent request to verified payment and webhook delivery.

  • Agent → NexFlow x402 endpoint
  • Facilitator cascade (CDP → PayAI → ...)
  • Chain verification (Base/USDC)
  • Webhooks → Your API
Agent
AI/LLM
NexFlow
x402 endpoint
Facilitator
CDP → PayAI → ...
Chain
Base/USDC
Webhooks
Your API

Built for any API

From LLM platforms to data APIs, agent services to SaaS backends.

LLM Platforms

Charge per token or completion

POST /v1/chat/completions
$0.002/1K tokens

Data APIs

Charge per query or record

GET /api/enrich?email=...
$0.01/request

Agent Services

Charge per task or action

POST /agents/execute
$0.05/task

SaaS APIs

Charge per call or unit

POST /api/process
$0.001/call

Multi‑facilitator cascade

NexFlow verifies each payment by trying facilitators in order, then falling back to on‑chain verification.

  1. CDP (Coinbase)
    Best for KYT/OFAC‑screened USDC on Base.
  2. 2
    PayAI
    Multi‑chain, multi‑token retail flows.
  3. 3
    OpenX402
    Permissionless, gasless verification and testing.
  4. 4
    Other facilitators
    e.g., Corbits, Mogami, x402.rs.
  5. 5
    On‑chain fallback
    Direct blockchain verification.
verification-loop.ts (TypeScript)
for (const facilitator of orderedFacilitators) {
  try {
    const result = await facilitator.verify(payment)
    if (result.success) {
      await updateHealth(facilitator.id, 'success')
      return result
    }
  } catch (error) {
    await updateHealth(facilitator.id, 'failure')
    continue // Try next facilitator
  }
}
// All facilitators failed, try on-chain
return await verifyOnChain(payment)

For Orchestrators & Routers

How a router or orchestrator calls a metered endpoint with x402 semantics.

1) Unpaid request (402 challenge)

curl https://api.nexflow.io/v1/metered/ep_xxx \
  -H "Authorization: Bearer sk_..."

# Response: 402 Payment Required
{
  "status": 402,
  "x402": {
    "version": "1",
    "accepts": [{
      "scheme": "exact",
      "network": "base",
      "token": "USDC",
      "maxAmount": "1000000",
      "resource": "https://api.nexflow.io/..."
    }]
  }
}

2) Paid request (verified 200)

curl https://api.nexflow.io/v1/metered/ep_xxx \
  -H "Authorization: Bearer sk_..." \
  -H "x-payment: 0x1234...abcd"

# Response: 200 OK
{
  "data": { ... },
  "x402": {
    "verified": true,
    "facilitator": "cdp",
    "txHash": "0x1234...abcd",
    "amount": "1000000",
    "token": "USDC"
  }
}

Verification is idempotent; routers can safely retry on network errors.

Ready to build?

Start accepting agent‑native payments in minutes.