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

# API discovery

> Advertise your paid endpoints so agents and registries can find price, networks, and how to call you.

**API discovery** lets agents and marketplaces learn what your API costs and how to pay **before** they call a protected route. Proceeds generates OpenAPI 3.1 discovery documents from your service and paywall configuration.

Discovery targets two ecosystems:

* [MPP discovery](https://mpp.dev/advanced/discovery) — Machine Payments Protocol registries and clients
* [x402scan](https://www.x402scan.com/discovery) — x402 service discovery and indexing

## Why it matters

Without discovery, an agent only learns your price after hitting `402`. With discovery, it can:

* Find your endpoints in a registry
* Read price, currency, and payment methods upfront
* Follow docs and guidance you publish for successful calls

If you sell to agents, treat discovery as part of go-to-market — same as a public OpenAPI spec for a free API.

## Documents Proceeds publishes

| Document                                                       | Scope                              |
| -------------------------------------------------------------- | ---------------------------------- |
| `https://myproceeds.xyz/api/x402/pay/{serviceId}/openapi.json` | Per-service x402 discovery         |
| `https://myproceeds.xyz/api/mpp/pay/{serviceId}/openapi.json`  | Per-service MPP discovery          |
| `https://myproceeds.xyz/openapi.json`                          | Platform-wide aggregate (x402scan) |

Payment URLs for individual paywalls stay the same:

```
https://myproceeds.xyz/api/x402/pay/{serviceId}/{slug}
https://myproceeds.xyz/api/mpp/pay/{serviceId}/{slug}
```

See [Payment URLs](/quickstart/add-a-paywall).

## What you configure in the dashboard

Open your service’s discovery settings and fill in:

| Field                        | Purpose                                                                   |
| ---------------------------- | ------------------------------------------------------------------------- |
| **Categories**               | Tags that help registries classify your API                               |
| **Contact email**            | Public contact for the discovery document                                 |
| **Docs homepage**            | Human docs landing page                                                   |
| **API reference**            | Link to your API reference                                                |
| **llms.txt / docs for LLMs** | Machine-readable docs agents can load                                     |
| **x-guidance**               | Short natural-language instructions for agents (how to use each endpoint) |
| **Public routes**            | Paths that are free (no `402`)                                            |

Proceeds can draft **x-guidance** from your paywall names and descriptions. Review it before publishing — clear guidance reduces failed paid calls.

## What agents see

Discovery documents include payment metadata such as:

* Endpoint paths and HTTP methods
* Price and currency (`USDC`)
* Supported networks and payment methods (`x402` and/or Tempo / MPP)

Tempo-only paywalls appear in MPP discovery; EVM paywalls appear in x402 discovery. A service that supports both can show up in both ecosystems.

## Publish and validate

1. Complete service metadata and enable the paywalls you want listed.
2. Open the discovery preview in the dashboard and fix any validation errors.
3. Confirm the public `openapi.json` URLs return your document.
4. Submit or sync with [x402scan](https://www.x402scan.com/discovery) and follow [MPP discovery](https://mpp.dev/advanced/discovery) guidance for registries you care about.

<Tip>
  Keep paywall **names** and **descriptions** accurate — they feed both human docs and auto-generated agent guidance.
</Tip>

## Related

* [Accept payments from agents](/guides/accept-payments-from-agents) — seller playbook for agent buyers
* [Pay with an agent](/agents/overview) — buyer tooling (AgentCash, Tempo Wallet, Circle)
* [MPP](https://mpp.dev/overview) and [x402](https://docs.x402.org/introduction) — protocol deep dives

<CardGroup cols={2}>
  <Card title="MPP discovery spec" icon="book" href="https://mpp.dev/advanced/discovery">
    How MPP clients expect OpenAPI payment terms.
  </Card>

  <Card title="x402scan discovery" icon="magnifying-glass" href="https://www.x402scan.com/discovery">
    Browse and publish x402-compatible APIs.
  </Card>
</CardGroup>