Proceeds doesn’t expose a traditional REST API for end users — the integration surface is the paywall URL itself. Each paywall generates URLs that follow the x402 and MPP standards.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.
Generated URLs
Replace{serviceId} and {slug} with the values from your dashboard.
Behavior
| Status | When |
|---|---|
402 Payment Required | The request arrived without a valid payment payload. The body contains a challenge with the price, supported networks, and accepted standards. |
2xx | Payment was verified and the upstream response was proxied. |
4xx from upstream | Payment was verified but the upstream rejected the request — check Events. |
5xx from upstream | Payment was verified but the upstream errored — check Events. |
Standards reference
x402
Open standard built on HTTP 402. Broadest client compatibility.
MPP
Machine Payments Protocol — for agents and machine-to-machine flows.
Circle Nanopayments
Gas-free USDC down to $0.000001 via batched settlement.
Concepts
Services, paywalls, transactions, and events.