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.

​
Exact vs Tiered

Price is a toggle on the paywall form:
  • Exact — one USDC price per request
  • Tiered — named tiers, each with its own USDC price. Buyers pick a tier when they pay. Proceeds sends the chosen name upstream as x-payment-tier.
For each tier, set a name and a price. Open the row chevron if that tier should override the upstream path or query parameters. The paywall list shows a min–max range when Tiered is on. Configure Tiered in the dashboard. The REST paywall create still takes a single Exact price.
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.