Skip to main content
Proceeds is payment infrastructure for APIs. Put a USDC paywall in front of any HTTP endpoint without changing your backend. Proceeds handles the payment challenge, verifies the payment, and proxies the request to your API. Proceeds is built for developers, agents, and API operators who need to charge per request, in real time, without subscriptions or API keys. These docs cover everything from creating your first paywall to running paid APIs in production.

​
What you can do

  • Charge per request in USDC, across GET, POST, PUT, and PATCH.
  • Group endpoints under a service with a single base URL and auth method.
  • Price each endpoint independently and override headers or query parameters per route.
  • Accept any standard — x402, MPP, or Circle Nanopayments — through the same paywall.
  • Settle across chains — Tempo, Base, Arc, and HyperEVM.
  • Inspect every transaction and event from the dashboard, in real time.

​
Who Proceeds is for

  • API operators who want to monetize per request without standing up subscriptions, billing accounts, or key issuance.
  • AI agent developers whose agents need to pay for inference, data, and tools autonomously.
  • Data and inference providers who want sub-cent pricing without rebuilding billing.

​
How it works

The flow follows HTTP 402 Payment Required:
1

Request

The client calls your protected URL.
2

Challenge

Proceeds returns 402 with a payment challenge — price, supported networks, and standards.
3

Pay

The client signs a payment using x402, MPP, or Circle Nanopayments.
4

Retry

The client retries the request with proof of payment.
5

Deliver

Proceeds verifies the payment and proxies the upstream response.
Read How it works for the full lifecycle, including transaction state and observability.

​
Get started

Add payments to your API

Create a service, add a paywall, and price your first endpoint in five minutes.

Test your paywall

Hit the generated URL with curl and confirm the 402 → pay → retry flow.

Concepts

Services, paywalls, transactions, and events — the four building blocks.

Standards

When to use x402, MPP, or Circle Nanopayments and how each maps to Proceeds.

Pay with an agent

Let an agent in Claude Code, Cursor, or Codex pay a Proceeds endpoint.