> ## 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](https://docs.myproceeds.xyz/quickstart/create-a-service.md) pointing at your origin, then [add a paywall](https://docs.myproceeds.xyz/quickstart/add-a-paywall.md) per billable route.

* Enable an EVM network (for example **Base**) so the challenge offers **x402**. 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** so the challenge offers **MPP**. 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)
* Connect Stripe and check that **Accept card payments (Stripe)** is on (it is by default) so the challenge can also offer MPP **Stripe charge**. Buyers with a card or a Link account can pay, and the money settles to your Stripe account. The charged price must be at least \$0.50 in whole cents. See [Accept cards and Link](https://docs.myproceeds.xyz/guides/accept-cards-and-link.md).

These are different rails on the same charge URL. 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/pay/{serviceId}/{slug}
```

You should get `402 Payment Required` with price and payment terms. The challenge lists every rail the paywall accepts, including MPP when Tempo is enabled, and cards and Link when [card payments](https://docs.myproceeds.xyz/guides/accept-cards-and-link.md) are on.

## 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/pay/{serviceId}/{slug}
```

Paste-ready buyer prompt:

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

The client picks x402, MPP, or Circle Nanopayments from the challenge on this URL.

Buyers typically use [AgentCash](https://docs.myproceeds.xyz/agents/agentcash.md) (x402 + MPP), [Tempo Wallet](https://docs.myproceeds.xyz/agents/tempo-wallet.md) (MPP), or [Circle Agent Stack](https://docs.myproceeds.xyz/agents/circle-agent-stack.md) (x402). Smoke-test yourself: [Make your first payment](https://docs.myproceeds.xyz/quickstart/make-your-first-payment.md) 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](https://docs.myproceeds.xyz/guides/api-discovery.md).

## 4. Watch the payment land

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

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

> [card] [Create a service](https://docs.myproceeds.xyz/quickstart/create-a-service.md)
>
> Start wrapping your API.

> [card] [Help agents call your API](https://docs.myproceeds.xyz/guides/api-discovery.md)
>
> Agent guidance and docs links on the service.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.