Skip to main content
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 — Machine Payments Protocol registries and clients
  • x402scan — 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

Payment URLs for individual paywalls stay the same:
See Payment URLs.

​
What you configure in the dashboard

Open your service’s discovery settings and fill in: 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 and follow MPP discovery guidance for registries you care about.
Keep paywall names and descriptions accurate — they feed both human docs and auto-generated agent guidance.

MPP discovery spec

How MPP clients expect OpenAPI payment terms.

x402scan discovery

Browse and publish x402-compatible APIs.