# Proceeds

> Add USDC paywalls to any API. Agents pay per request — no accounts, no API keys, no subscriptions.

- [What is Proceeds?](https://docs.myproceeds.xyz/index.md): Wrap any HTTP API with a USDC paywall. Agents pay per request over x402 or MPP.
- [Create a service](https://docs.myproceeds.xyz/quickstart/create-a-service.md): Point Proceeds at your API. One service per product — then add paywalls under it.
- [Add a paywall](https://docs.myproceeds.xyz/quickstart/add-a-paywall.md): Price a route under a service. Agents hit the URL, pay the 402, and get your API response.
- [Monitor payments](https://docs.myproceeds.xyz/quickstart/monitor-payments.md): Track transactions, lifecycle events, webhooks, and revenue once payments are flowing.
- [Test paywalls](https://docs.myproceeds.xyz/quickstart/test-paywalls.md): Exercise paywalls on testnet with faucet funds, or use the console Test Payment flow.
- [Set up an agent wallet](https://docs.myproceeds.xyz/quickstart/set-up-an-agent-wallet.md): Install an agent IDE, drop a wallet setup prompt, and fund with real USDC so your agent can pay.
- [Make your first payment](https://docs.myproceeds.xyz/quickstart/make-your-first-payment.md): Ask your funded agent to find a paid resource, pay the 402, and return the response.
- [Sell to agents](https://docs.myproceeds.xyz/guides/accept-payments-from-agents.md): Wrap your API, share a charge URL, get paid per request over x402 or MPP.
- [Help agents call your API](https://docs.myproceeds.xyz/guides/api-discovery.md): Add agent guidance and docs links on the service. Share charge URLs yourself.
- [Configure pricing](https://docs.myproceeds.xyz/guides/configure-pricing.md): Set per-endpoint USDC prices, including sub-cent amounts.
- [Forward upstream auth](https://docs.myproceeds.xyz/guides/forward-upstream-auth.md): Keep upstream API credentials inside Proceeds so clients never see them.
- [Custom headers and query parameters](https://docs.myproceeds.xyz/guides/custom-headers-and-params.md): Forward extra request data to the upstream on a per-paywall basis.
- [Restrict HTTP methods](https://docs.myproceeds.xyz/guides/restrict-http-methods.md): Limit a paywall to specific HTTP methods so you only charge for the calls you intend to.
- [Settle to a wallet or bank](https://docs.myproceeds.xyz/guides/settle-to-wallet-or-bank.md): Withdraw USDC to a wallet you control, or off-ramp to a US bank account via ACH.
- [Supported blockchains](https://docs.myproceeds.xyz/guides/supported-blockchains.md): Networks Proceeds supports today and how to test against their testnets.
- [Production checklist](https://docs.myproceeds.xyz/guides/production-checklist.md): Confirm settings before moving a service from testnet to mainnet.
- [Troubleshooting](https://docs.myproceeds.xyz/guides/troubleshooting.md): Resolve challenge, payment, and fulfillment failures.
- [Concepts](https://docs.myproceeds.xyz/concepts.md): Services, paywalls, transactions, events, and wallets — the building blocks of Proceeds.
- [How it works](https://docs.myproceeds.xyz/how-it-works.md): The Proceeds payment lifecycle, from request to fulfillment, and where to observe each step.
- [Paywalls](https://docs.myproceeds.xyz/dashboard/paywalls.md): Group your API endpoints under services and start earning.
- [Transactions](https://docs.myproceeds.xyz/dashboard/transactions.md): Every payment attempt against your paywalls, with the state to reconcile revenue and debug failures.
- [Events](https://docs.myproceeds.xyz/dashboard/events.md): The step-by-step trail every paid request leaves behind — your first stop when something fails.
- [Wallet](https://docs.myproceeds.xyz/dashboard/wallet.md): Where your USDC accumulates — and how you withdraw it to a wallet or a bank account.
- [API Keys](https://docs.myproceeds.xyz/dashboard/api-keys.md): Programmatic access to the Proceeds API. Each key is shown once — store it securely.
- [Webhooks](https://docs.myproceeds.xyz/dashboard/webhooks.md): Receive signed HTTP callbacks when payments, paywalls, and services change in your account.
- [REST API](https://docs.myproceeds.xyz/api-reference/overview.md): Programmatically manage Proceeds services and paywalls over a REST API authenticated with API keys.
- [Authentication](https://docs.myproceeds.xyz/api-reference/authentication.md): Authenticate REST API requests with a Proceeds API key, scoped per endpoint.
- [Errors & rate limits](https://docs.myproceeds.xyz/api-reference/errors-and-rate-limits.md): Error response shape, machine-readable codes, and per-key rate limits for the Proceeds REST API.
- [Health check](https://docs.myproceeds.xyz/api-reference/system/health-check.md): Unauthenticated liveness + readiness probe — no API key required. Returns `200` with `status: ok` when the API is serving and its database is reachable, or `503` with `status: degraded` when a dependency check fails. Intended for uptime monitors and load balancers.
- [List services](https://docs.myproceeds.xyz/api-reference/services/list-services.md): List the tenant's services with their paywalls. `authConfig` values are masked (`"***"`) — only the field names are returned.
- [Create a service](https://docs.myproceeds.xyz/api-reference/services/create-a-service.md)
- [Get a service](https://docs.myproceeds.xyz/api-reference/services/get-a-service.md)
- [Delete a service](https://docs.myproceeds.xyz/api-reference/services/delete-a-service.md): Deletes the service and all its paywalls atomically.
- [Update a service](https://docs.myproceeds.xyz/api-reference/services/update-a-service.md): Partial update. Only provided fields are modified.
- [List paywalls](https://docs.myproceeds.xyz/api-reference/paywalls/list-paywalls.md)
- [Create a paywall](https://docs.myproceeds.xyz/api-reference/paywalls/create-a-paywall.md): Paywalls always settle to the tenant's own wallet — the merchant wallet is set automatically to the tenant's primary wallet and is not accepted as a parameter. Slugs must be unique within the parent service (`serviceId` + `slug`).
- [Get a paywall](https://docs.myproceeds.xyz/api-reference/paywalls/get-a-paywall.md)
- [Delete a paywall](https://docs.myproceeds.xyz/api-reference/paywalls/delete-a-paywall.md)
- [Update a paywall](https://docs.myproceeds.xyz/api-reference/paywalls/update-a-paywall.md): Partial update. Only provided fields are modified.
- [Validate the API key and return its tenant + scopes](https://docs.myproceeds.xyz/api-reference/identity/validate-the-api-key-and-return-its-tenant-+-scopes.md): Any valid (non-revoked, non-expired) key works; no scope required.
- [List the tenant's payment transactions](https://docs.myproceeds.xyz/api-reference/data/list-the-tenants-payment-transactions.md)
- [List the tenant's events](https://docs.myproceeds.xyz/api-reference/data/list-the-tenants-events.md): Per-eventType counts are returned in `meta.stats`. The cached upstream response body is not exposed.
- [Proceeds CLI](https://docs.myproceeds.xyz/cli/overview.md): Manage Proceeds services, paywalls, transactions, and events from your terminal or AI agent.
- [Install the Proceeds CLI](https://docs.myproceeds.xyz/cli/install.md): Install the Proceeds CLI with npm.
- [CLI authentication](https://docs.myproceeds.xyz/cli/authentication.md): Authenticate the Proceeds CLI with a console API key.
- [Services](https://docs.myproceeds.xyz/cli/services.md): Create, list, get, update, and delete Proceeds services from the CLI.
- [Paywalls](https://docs.myproceeds.xyz/cli/paywalls.md): Create, list, get, update, and delete Proceeds paywalls from the CLI.
- [Transactions and events](https://docs.myproceeds.xyz/cli/transactions.md): List payment transactions and analytics events from the Proceeds CLI.
- [Pay with an agent](https://docs.myproceeds.xyz/agents/overview.md): Let an AI agent in Claude Code, Cursor, or Codex pay a Proceeds endpoint over x402, MPP, or Circle Nanopayments.
- [AgentCash](https://docs.myproceeds.xyz/agents/agentcash.md): Give your agent one USDC balance to pay Proceeds endpoints over x402 or MPP — no API keys.
- [Circle Agent Stack](https://docs.myproceeds.xyz/agents/circle-agent-stack.md): Use Circle CLI and Agent Wallets to pay Proceeds endpoints over x402, including sub-cent nanopayments.
- [Tempo Wallet](https://docs.myproceeds.xyz/agents/tempo-wallet.md): Pay MPP-enabled Proceeds endpoints from your agent with the Tempo Wallet's built-in spend controls.

## OpenAPI Specs

- [openapi](/openapi.yaml)