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.
Give your agent these docs
Before wiring up a wallet, let your agent read the documentation directly: MCP server — search and read tools for these docs:Before you start
You need:- A Proceeds payment URL for the endpoint you want to call:
- A funded agent wallet with USDC on a supported network — see Supported blockchains.
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.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 land as
Completed in Transactions (nanopayments go Pending → Completed after Gateway batch settlement), 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.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.
API discovery
How sellers publish endpoints agents can find.
Accept payments from agents
Seller playbook for agent buyers.

