Skip to main content
Separate from the REST management API, each paywall exposes payment URLs that buyers call directly. These follow the x402 and MPP standards — a buyer requests the URL, receives a 402 Payment Required challenge, pays, and retries.

​
Generated URLs

Replace {serviceId} and {slug} with the values from your dashboard. 
POST https://myproceeds.xyz/api/x402/pay/{serviceId}/{slug}
POST https://myproceeds.xyz/api/mpp/pay/{serviceId}/{slug}
Every paywall exposes the x402 URL. The MPP URL is available when Tempo is one of the paywall’s supported networks.

​
Behavior

StatusWhen
402 Payment RequiredThe request arrived without a valid payment payload. The body contains a challenge with the price, supported networks, and accepted standards.
2xxPayment was verified and the upstream response was proxied.
4xx from upstreamPayment was verified but the upstream rejected the request — check Events.
5xx from upstreamPayment 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.

Pay with an agent

Call these URLs from an agent in Claude Code, Cursor, or Codex.