Solutions

Charge per request without accounts, invoices, or prepaid balances.

Protect a route with x402 middleware, set a price, and receive stablecoins when each clearing cycle settles. Buyers do not need an account, invoice, or prepaid balance.

Set a price per route

Set a price for each endpoint and let any x402-compatible buyer pay on the first request.

Verify before doing the work

Return 402 before running expensive work, and respond only after Core accepts the guarantee.

Clear payment records

High-frequency requests settle as net positions, with a guarantee record behind every amount.

Use cases

Built for api providers workflows

Give each stakeholder the payment primitives they need: instant authorization, clear limits, and settlement that stays easy to audit.

For API and platform teams

Monetize per call

Charge for inference, data, search, compute, or premium actions one request at a time.

Skip the signup funnel

Buyers can make a paid request without creating an account, receiving an API key, or adding a prepaid balance.

Charge small amounts

Without an on-chain transaction for each request, settlement costs do not consume small payments.

For finance and ops

Settle in stablecoins

Receive payment in the assets enabled by your deployment. USDC and USDT are common defaults.

Audit each payment

Trace every net settlement back to the guarantees and certificates that produced it.

Process

Start with api providers in 3 steps

The path is deliberately small: configure the payment session, verify each request, then settle the cycle with durable records.

  1. 01

    Protect a route

    Add the payment middleware to one endpoint and configure scheme, network, asset, price, and payTo.

  2. 02

    Verify, then serve

    The middleware returns 402 with your price, checks the guarantee through the facilitator, and releases the response.

  3. 03

    Get paid each cycle

    Accepted guarantees settle as net positions, without an on-chain transaction for every request.

FAQ

Common questions about api providers

Do buyers need an account with us first?

No. A buyer arrives with collateral-backed credit and pays on the first request, so there is no signup, key issuance, or prepaid balance in front of your revenue.

What happens if a buyer cannot cover the request?

Core rejects an under-backed guarantee, so no certificate is returned and you simply do not serve the work. Keep anything expensive behind that check.

Which frameworks are supported?

TypeScript and Python middleware covering Express, Hono, Next.js, Nuxt, SvelteKit, Remix, Bun, FastAPI, and Flask, plus the edge-safe server primitive for anything else.

Can we still price dynamically?

Yes. Fixed prices are advertised in the 402 response, and for variable work you can quote a task with a maximum amount, expiry, and completion rules.

Something else on your mind?Contact us

Ready to build for api providers?