Skip to main content
Proceeds puts a USDC paywall in front of any HTTP endpoint without changing your backend. You wrap a route, share a charge URL, an agent pays the 402, and the money lands in your Proceeds wallet. When money starts moving, run the business from the dashboard: Transactions, Events, Webhooks to your server, and Wallet to withdraw onchain or off-ramp to a US bank via ACH.

​
The seller path

1

Wrap your API

Create a service pointing at your origin, then add a paywall for each billable route. Pick Testnet while you build.
2

Get a 402

Copy the charge URL and request it unpaid:
You should get 402 Payment Required with price and payment terms. That URL is what you give buyers.
3

An agent pays — money lands

Point a funded agent at that URL. It pays the 402 and retries; Proceeds verifies and proxies your API response. Confirm the payment on Transactions and the balance on Wallet.

Create a service

Point Proceeds at your origin.

Add a paywall

Price a route and copy the charge URLs.
x402 and MPP are different rails. Don’t treat them as one protocol.
HTTP 402 Payment Required with a facilitator. Every paywall gets an x402 URL. Enable an EVM network (for example Base) on the service.
Protocol docs: x402 seller quickstart. Use those when you self-host middleware. Use Proceeds when you want the wrap without touching your server.
Peer-to-peer Machine Payments Protocol: no facilitator, wallet UI, receipts. Enable Tempo on the service to get MPP URLs. Agents typically pay with Tempo Wallet or AgentCash.
Protocol docs: MPP server quickstart. Use those when you embed mppx in your own server. Use Proceeds when you want the wrap.

​
Prerequisites

You don’t need to be a blockchain developer. If you can deploy an HTTP API and run curl, you can sell.

​
How the docs are organized

  • Getting Started — wrap a service, add a paywall, test the 402, watch the first payment
  • Guides — sell to agents, pricing, headers, settlement, production
  • Manage — dashboard: paywalls, transactions, events, wallet, API keys, webhooks
  • API Reference — REST for services, paywalls, transactions, and events
  • Agent Wallets — tools buyers use to pay your URLs

​
Buying instead of selling?

If you are an agent trying to pay someone else’s endpoint, start at Set up an agent wallet.
Building on testnet? See Test paywalls for faucets and the console Test Payment flow.