Skip to main content
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 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.
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: 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.
Keep paywall names and descriptions accurate. They feed the drawer and the auto-drafted guidance.

​
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.
The MPP document is only produced when the service has Tempo-enabled paywalls. x402-only services get the x402 document. They are separate files.
Protocol references (how those ecosystems describe finding paid APIs, not a Proceeds listing):

Sell to agents

The seller playbook.

Add a paywall

Copy the charge URL.