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.Documentation Index
Fetch the complete documentation index at: https://docs.myproceeds.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Set a price
In Paywalls, edit a paywall and set Price to the USDC amount you want to charge per request.| Range | Use case |
|---|---|
< $0.01 | Per-token inference, per-query data lookups, per-call agent tools. Use Circle Nanopayments. |
$0.01 – $1.00 | Standard per-call API monetization. x402 or MPP both work well. |
> $1.00 | Higher-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.Next
Standards
How x402, MPP, and Circle Nanopayments handle different price ranges.
Wallet
See balances across rails and chains as priced requests come in.