Skip to main content
The Tempo Wallet is a managed MPP client with built-in spend controls and service discovery. Agents use the tempo wallet command to discover and pay MPP-enabled services on demand — including any Tempo-enabled Proceeds paywall. Use Tempo Wallet when your target paywall exposes an MPP URL and you want first-class Tempo support with spending guardrails.

​
Install

Tempo Wallet works in Claude Code, Cursor, and Codex. Log in to create and connect a managed wallet: 
tempo wallet login
Fund the wallet with USDC.

​
Pay a Proceeds endpoint

A Proceeds paywall exposes an MPP URL when Tempo is one of its supported networks: 
https://myproceeds.xyz/api/mpp/pay/{serviceId}/{slug}
Hand the URL to your agent and let the Tempo Wallet handle the 402 challenge, sign the payment, and retry: 
Pay https://myproceeds.xyz/api/mpp/pay/{serviceId}/{slug} with my Tempo Wallet and return the response.
No MPP URL? Confirm Tempo is selected under the paywall’s Networks. Otherwise use the x402 URL with AgentCash or Circle Agent Stack. See Troubleshooting.
For quick manual testing without the managed wallet, the mppx CLI also handles the challenge and retry: 
npx mppx https://myproceeds.xyz/api/mpp/pay/{serviceId}/{slug}

​
Confirm the payment

Watch the matching transaction move from Pending to Completed in Transactions, and trace Request → Payment → Fulfillment in Events. MPP returns a Payment-Receipt header on success.

​
When to use Tempo Wallet

  • Your target paywall accepts MPP (Tempo is in its supported networks).
  • You want built-in spend controls and service discovery from a managed wallet.
  • You want first-class Tempo support for machine-to-machine payments.

MPP agent quickstart

Tempo Wallet setup and the full agent tool comparison.

Agents overview

Compare Tempo Wallet with AgentCash and Circle Agent Stack.

MPP standard

The machine-to-machine flow Tempo Wallet uses against Proceeds.

Test your paywall

Confirm the MPP URL works before pointing an agent at it.