> ## 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.

# Pay with an agent

> Let an AI agent in Claude Code, Cursor, or Codex pay a Proceeds endpoint over x402, MPP, or Circle Nanopayments.

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 funded **agent wallet** with USDC on a supported network — see [Supported blockchains](/guides/supported-blockchains).

<Note>
  A paywall only exposes an MPP URL when **Tempo** is one of its supported networks. Every paywall exposes an x402 URL.
</Note>

## 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.

| Tool                                             | Best for                                            | Standards                 | Proceeds URL                                |
| ------------------------------------------------ | --------------------------------------------------- | ------------------------- | ------------------------------------------- |
| [AgentCash](/agents/agentcash)                   | Broad access and service discovery across 300+ APIs | x402, MPP                 | Either — the agent picks from the challenge |
| [Circle Agent Stack](/agents/circle-agent-stack) | Circle-native wallets and sub-cent nanopayments     | x402, Circle Nanopayments | `/api/x402/pay/{serviceId}/{slug}`          |
| [Tempo Wallet](/agents/tempo-wallet)             | MPP-first agents with built-in spend controls       | MPP                       | `/api/mpp/pay/{serviceId}/{slug}`           |

## Use from your IDE

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

<Steps>
  <Step title="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).
  </Step>

  <Step title="Fund a wallet">
    Onboard and fund an agent wallet with USDC.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Confirm in the dashboard">
    Watch the matching record move from `Pending` to `Completed` in [Transactions](/dashboard/transactions), and trace each step in [Events](/dashboard/events).
  </Step>
</Steps>

## 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.

```bash theme={null}
# 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

```mermaid theme={null}
flowchart TD
  Dev[You in Claude Code, Cursor, or Codex] --> Tool{Which tool?}
  Tool -->|x402 or MPP| AgentCash[AgentCash]
  Tool -->|x402 or nanopayments| Circle[Circle Agent Stack]
  Tool -->|MPP| Tempo[Tempo Wallet]
  AgentCash --> Call[Agent calls Proceeds URL]
  Circle --> Call
  Tempo --> Call
  Call --> Challenge["Proceeds returns 402 challenge"]
  Challenge --> Pay[Agent signs payment from its wallet]
  Pay --> Retry[Agent retries with proof]
  Retry --> Deliver[Proceeds verifies and proxies upstream]
  Deliver --> Monitor[Track in Transactions and Events]
```

## Next steps

<CardGroup cols={3}>
  <Card title="AgentCash" icon="store" href="/agents/agentcash">
    300+ APIs over x402 and MPP from one USDC balance.
  </Card>

  <Card title="Circle Agent Stack" icon="wallet" href="/agents/circle-agent-stack">
    Agent wallets and gas-free nanopayments via Circle CLI.
  </Card>

  <Card title="Tempo Wallet" icon="bolt" href="/agents/tempo-wallet">
    MPP-native payments with built-in spend controls.
  </Card>
</CardGroup>