Skip to main content
Each paywall has its own price, denominated in USDC. Pricing lives on the paywall, not the service, so a single service can mix free routes, micro-priced routes, and high-value routes.

​
Set a price

In Paywalls, edit a paywall and set Price to the USDC amount you want to charge per request.
RangeUse case
< $0.01Per-token inference, per-query data lookups, per-call agent tools. Use Circle Nanopayments.
$0.01 – $1.00Standard per-call API monetization. x402 or MPP both work well.
> $1.00Higher-value endpoints — premium data, premium models, batch jobs.
Sub-cent pricing requires a payment method that supports it. Today that’s Circle Nanopayments via Circle Gateway.

​
Mix paid and free routes

Not every endpoint has to be paid. Add paywalls only to the routes you want to monetize; unprotected routes on your origin remain free and aren’t proxied through Proceeds.

​
Change a price

Editing Price on a paywall takes effect on the next request. Existing in-flight payments are unaffected.
When you change a price, also update any client-side caches that store the challenge. Stale challenges will be rejected at verification.

​
Next

Standards

How x402, MPP, and Circle Nanopayments handle different price ranges.

Wallet

See balances across rails and chains as priced requests come in.