> ## 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.

# What is Proceeds?

> Wrap any HTTP API with a USDC paywall. Agents pay per request over x402 or MPP.

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](/dashboard/transactions), [Events](/dashboard/events), [Webhooks](/dashboard/webhooks) to your server, and [Wallet](/dashboard/wallet) to withdraw onchain or off-ramp to a US bank via ACH.

## The seller path

<Steps>
  <Step title="Wrap your API">
    [Create a service](/quickstart/create-a-service) pointing at your origin, then [add a paywall](/quickstart/add-a-paywall) for each billable route. Pick **Testnet** while you build.
  </Step>

  <Step title="Get a 402">
    Copy the charge URL and request it unpaid:

    ```bash theme={null}
    curl -i https://myproceeds.xyz/api/x402/pay/{serviceId}/{slug}
    ```

    You should get `402 Payment Required` with price and payment terms. That URL is what you give buyers.
  </Step>

  <Step title="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](/dashboard/transactions) and the balance on [Wallet](/dashboard/wallet).

    ```text theme={null}
    Call https://myproceeds.xyz/api/x402/pay/{serviceId}/{slug} and pay if challenged. Return the response body.
    ```
  </Step>
</Steps>

<CardGroup cols={2}>
  <Card title="Create a service" icon="server" href="/quickstart/create-a-service">
    Point Proceeds at your origin.
  </Card>

  <Card title="Add a paywall" icon="tag" href="/quickstart/add-a-paywall">
    Price a route and copy the charge URLs.
  </Card>
</CardGroup>

x402 and MPP are different rails. Don't treat them as one protocol.

<AccordionGroup>
  <Accordion title="x402 — simpler seller path">
    HTTP `402 Payment Required` with a facilitator. Every paywall gets an x402 URL. Enable an EVM network (for example Base) on the service.

    ```text theme={null}
    https://myproceeds.xyz/api/x402/pay/{serviceId}/{slug}
    ```

    Protocol docs: [x402 seller quickstart](https://docs.x402.org/getting-started/quickstart-for-sellers). Use those when you self-host middleware. Use Proceeds when you want the wrap without touching your server.
  </Accordion>

  <Accordion title="MPP — better buyer DX, less volume">
    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.

    ```text theme={null}
    https://myproceeds.xyz/api/mpp/pay/{serviceId}/{slug}
    ```

    Protocol docs: [MPP server quickstart](https://mpp.dev/quickstart/server). Use those when you embed `mppx` in your own server. Use Proceeds when you want the wrap.
  </Accordion>
</AccordionGroup>

## Prerequisites

* A public HTTP API you can point Proceeds at
* A Proceeds account at [myproceeds.xyz](https://myproceeds.xyz)
* **USDC** prices (6 decimals). [What is USDC](https://developers.circle.com/stablecoins/what-is-usdc)

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](/quickstart/set-up-an-agent-wallet).

<Tip>
  Building on testnet? See [Test paywalls](/quickstart/test-paywalls) for faucets and the console **Test Payment** flow.
</Tip>