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

# Sell to agents

> Wrap your API, share a charge URL, get paid per request over x402 or MPP.

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](/quickstart/create-a-service) pointing at your origin, then [add a paywall](/quickstart/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](https://docs.x402.org/getting-started/quickstart-for-sellers)
* 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](https://mpp.dev/quickstart/server)

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

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

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

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

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

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

Paste-ready buyer prompt:

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

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](/agents/agentcash) (x402 + MPP), [Tempo Wallet](/agents/tempo-wallet) (MPP), or [Circle Agent Stack](/agents/circle-agent-stack) (x402). Smoke-test yourself: [Make your first payment](/quickstart/make-your-first-payment) or the console **Test Payment** flow.

<Note>
  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](/guides/api-discovery).
</Note>

## 4. Watch the payment land

* [Transactions](/dashboard/transactions) for payment state (`Completed` / `Failed`)
* [Events](/dashboard/events) for the request trail (`REQUEST` → `SUCCESS`)
* [Webhooks](/dashboard/webhooks) if your backend should react
* [Wallet](/dashboard/wallet) to withdraw onchain or [off-ramp to a bank](/guides/settle-to-wallet-or-bank)

## 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](/guides/configure-pricing). Don't assume nanopayments on Base are instant.

<CardGroup cols={2}>
  <Card title="Create a service" icon="server" href="/quickstart/create-a-service">
    Start wrapping your API.
  </Card>

  <Card title="Help agents call your API" icon="megaphone" href="/guides/api-discovery">
    Agent guidance and docs links on the service.
  </Card>
</CardGroup>