Skip to main content
Agents don’t sign up, enter cards, or wait for an invoice. They can pay an HTTP 402 in the same request. Proceeds is how you sell to them: wrap your API, share a charge URL, and watch the payment land. You do not install protocol middleware, and you do not need a marketplace listing.

​
What you will do

  1. Wrap your API with a service and paywalls
  2. Confirm the unpaid URL returns 402
  3. Share the payment URL
  4. Watch the payment land, then settle

​
1. Wrap and price your API

Create a service pointing at your origin, then add a paywall per billable route.
  • Enable an EVM network (for example Base) for x402 URLs. x402 is the simpler plug-and-play seller path — HTTP 402 plus a facilitator. x402 seller quickstart
  • Enable Tempo if you want MPP URLs. MPP is peer-to-peer (no facilitator, wallet UI, receipts) and a better buyer experience, with less ecosystem volume today. MPP server quickstart
These are different rails. A service can expose both. Prefer clear slugs and descriptions — they show up on the paywall and in the per-service overflow drawer.

​
2. Confirm the 402

You should get 402 Payment Required with price and payment terms. If you enabled Tempo, the MPP URL challenges the same way:

​
3. Share the payment URL

This is the go-to-market step: copy the payment URL from the paywall and put it in your docs, llms.txt, README, or a prompt you give buyers.
Paste-ready buyer prompt:
If you enabled Tempo, the paywall also has a separate MPP URL. That is not the same endpoint. Circle Nanopayments are not a third URL. Buyers typically use AgentCash (x402 + MPP), Tempo Wallet (MPP), or Circle Agent Stack (x402). Smoke-test yourself: Make your first payment or the console Test Payment flow.
Proceeds does not list your API on x402scan, MPPScan, or a marketplace. Share the charge URL yourself. Use the per-service overflow drawer to write agent guidance and link your own docs — see Help agents call your API.

​
4. Watch the payment land

​
Tips

  • Write Agent guidance in the per-service overflow drawer as instructions to an agent, not marketing copy
  • Mark health and docs paths as Free routes so agents don’t pay for them
  • For sub-cent prices, see Configure pricing. Don’t assume nanopayments on Base are instant.

Create a service

Start wrapping your API.

Help agents call your API

Agent guidance and docs links on the service.