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

# Help agents call your API

> Add agent guidance and docs links on the service. Share charge URLs yourself.

On each service, the dashboard overflow menu opens a drawer where you write agent guidance, link your docs, and mark free routes. That metadata helps an agent succeed after you hand them a charge URL.

Proceeds does **not** list your API on x402scan, MPPScan, the MPP directory, or any marketplace. Public registry listing is not a Proceeds go-to-market path today.

## What to do instead

1. [Add a paywall](/quickstart/add-a-paywall) and copy the charge URL.
2. Open the per-service overflow drawer and fill in guidance an agent can follow.
3. Put the charge URL in your README, `llms.txt`, docs, or a setup prompt.

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

An unpaid GET to that URL returns `402` with price and payment terms. That challenge is how a compatible client learns cost — you do not need a registry for the payment to work.

## What you configure

On the service overflow menu, open the drawer:

| Field                        | Purpose                                                     |
| ---------------------------- | ----------------------------------------------------------- |
| **Categories**               | Tags you choose for your own docs                           |
| **Contact email**            | Public contact if you want one on the generated OpenAPI doc |
| **Homepage**                 | Your human docs landing page                                |
| **API reference**            | Link to your API reference                                  |
| **llms.txt / docs for LLMs** | Machine-readable docs agents can load                       |
| **Agent guidance**           | Short instructions for how to call each endpoint            |
| **Free routes**              | Paths that should not return `402`                          |
| **Wallet-gated routes**      | Paths that require wallet auth but no payment               |

Proceeds auto-drafts **Agent guidance** from paywall names and descriptions. Review it before saving — write it as instructions to an agent, not marketing copy.

Only **enabled** paywalls are included.

<Tip>
  Keep paywall **names** and **descriptions** accurate. They feed the drawer and the auto-drafted guidance.
</Tip>

## Generated OpenAPI docs

The drawer can generate OpenAPI documents from your service and paywalls. Copy the URL from the drawer if you want to host it or hand it to an agent. Treat it as a file you share, not a listing.

When **Homepage** or **API reference** is set, the generated spec includes `externalDocs.url` (API reference if set, otherwise homepage). Agent-readiness scorers that look for that field can score a Proceeds wrap Fully agent-ready and runtime-verified. That is not a listing.

<Note>
  The MPP document is only produced when the service has Tempo-enabled paywalls. x402-only services get the x402 document. They are separate files.
</Note>

Protocol references (how those ecosystems describe finding paid APIs, not a Proceeds listing):

* [MPP discovery](https://mpp.dev/advanced/discovery)
* [x402 seller quickstart](https://docs.x402.org/getting-started/quickstart-for-sellers)

## Related

* [Sell to agents](/guides/accept-payments-from-agents) — wrap, share a URL, get paid
* [Pay with an agent](/agents/overview) — buyer wallets (AgentCash, Tempo Wallet, Circle)

<CardGroup cols={2}>
  <Card title="Sell to agents" icon="robot" href="/guides/accept-payments-from-agents">
    The seller playbook.
  </Card>

  <Card title="Add a paywall" icon="tag" href="/quickstart/add-a-paywall">
    Copy the charge URL.
  </Card>
</CardGroup>