Skip to main content
These docs mostly cover the seller journey — putting a paywall in front of your API. This section covers the buyer journey: you already have a Proceeds payment URL, and you want an AI agent to pay it for you. Agents pay Proceeds endpoints the same way any client does — request, get a 402 challenge, sign a payment, retry. The difference is the wallet and tooling live inside your agent. Pick a tool below, install it in your IDE, fund a wallet, then hand your agent a Proceeds URL.

​
Before you start

You need:
  • A Proceeds payment URL for the endpoint you want to call:
https://myproceeds.xyz/api/x402/pay/{serviceId}/{slug}
https://myproceeds.xyz/api/mpp/pay/{serviceId}/{slug}
A paywall only exposes an MPP URL when Tempo is one of its supported networks. Every paywall exposes an x402 URL.

​
Pick your tool

All three tools work from Claude Code, Cursor, and Codex. Choose based on the standard your target paywall accepts and the wallet experience you want.
ToolBest forStandardsProceeds URL
AgentCashBroad access and service discovery across 300+ APIsx402, MPPEither — the agent picks from the challenge
Circle Agent StackCircle-native wallets and sub-cent nanopaymentsx402, Circle Nanopayments/api/x402/pay/{serviceId}/{slug}
Tempo WalletMPP-first agents with built-in spend controlsMPP/api/mpp/pay/{serviceId}/{slug}

​
Use from your IDE

The setup pattern is the same across Claude Code, Cursor, and Codex:
1

Install the CLI or skill

Each tool ships a CLI, an agent skill, or an MCP server. Install it once in the IDE where your agent runs (see the per-tool pages for the exact command).
2

Fund a wallet

Onboard and fund an agent wallet with USDC.
3

Hand the agent a Proceeds URL

Give your agent the paywall URL and ask it to call the endpoint. The agent handles the 402 challenge, signs the payment, and retries automatically.
4

Confirm in the dashboard

Watch the matching record move from Pending to Completed in Transactions, and trace each step in Events.

​
Proceeds URL cheat sheet

Both URLs point at the same paywall and proxy to the same upstream. The difference is the payment standard the client speaks. 
# x402 — broad compatibility, works with any x402-aware agent
https://myproceeds.xyz/api/x402/pay/{serviceId}/{slug}

# MPP — machine-to-machine, Tempo-enabled paywalls only
https://myproceeds.xyz/api/mpp/pay/{serviceId}/{slug}

​
How an agent payment flows

​
Next steps

AgentCash

300+ APIs over x402 and MPP from one USDC balance.

Circle Agent Stack

Agent wallets and gas-free nanopayments via Circle CLI.

Tempo Wallet

MPP-native payments with built-in spend controls.