x402 Preflight

x402 Preflight · docs · x402 vs Stripe

x402 vs Stripe: per-call billing for APIs

They solve different problems. x402 is an open, HTTP-native rail for machine-to-machine, per-call payments settled in stablecoin; Stripe is a card and subscription stack for human checkout. For sub-cent API calls, card rails carry fixed fees that make the economics hard; x402 moves the payment into the request itself.

Quick comparison

When x402 is the wrong tool

Human checkout, refunds, chargebacks and subscriptions are Stripe's ground. x402 does not provide those flows, and it is not a consumer checkout product.

When Stripe is the wrong tool

An autonomous agent making thousands of tiny calls per day: a fixed per-charge fee dwarfs the amount, and no human is present to complete checkout.

What this does NOT prove

Choosing a rail does not itself prove your endpoint charges correctly or that any catalogue indexes it. Verify the live challenge — that is a separate check.

Check your own endpoint (free, read-only)

curl -s -X POST https://x402.chikocorp.com/api/preflight/inspect \
  -H 'content-type: application/json' \
  -d '{"resource_url":"https://your-api.example.com/resource","method":"GET"}'

Deeper read: the technical audit is 0.05 USDC and the full diagnostic report 5 USDC, paid in USDC on Base and delivered by API. Monthly monitoring is 29 USDC/month.

Frequently asked questions

Is x402 a Stripe replacement?

Not for human checkout. x402 targets machine-to-machine, per-call payments; Stripe targets cards, subscriptions and hosted checkout for people.

Can I use both x402 and Stripe?

Yes. Many APIs keep Stripe for human billing and add x402 for agent/API per-call access.

More answers for x402 API developers — back to x402 Preflight.