Unlike x402 which only supports on-chain USDC, MPP adds Tempo network stablecoins and traditional card payments as additional options.
How It Works
Detailed Flow
- Agent calls
GET /mpp/purchase?plan=<plan>without payment credentials - MPP service returns 402 with a
WWW-Authenticate: Paymentchallenge containing amount, currency, and recipient - Agent signs the payment using Tempo Wallet or Stripe
- Agent retries the purchase request with
Authorization: Paymentcredential - MPP service verifies payment, creates a subscription, and returns an API Key
Supported Payment Methods
API Endpoints
Pricing Response
Purchase Response (Success)
CLI Usage
The ChainStream CLI supports MPP as a payment option during the auto-purchase flow:Manual Integration (Tempo Wallet)
Setup
Install the Tempo Wallet CLI and log in (one-time passkey authentication via browser):Tempo Wallet uses passkey (WebAuthn) authentication. The first setup requires a browser interaction. After that, the session persists and agent operations work without further browser interaction.
Purchase
WWW-Authenticate: Payment challenge automatically, signs the transaction, and returns the API Key on success.
Compatible Wallets
Tempo is EVM-compatible (chain ID 4217). Any wallet holding USDC.e on Tempo works:- Tempo Wallet CLI (
tempo request) — recommended, passkey auth, built-in MPP support - Any EVM wallet (MetaMask, Coinbase CDP, Privy) — add Tempo as custom network
MPP vs x402
Next Steps
x402 Payment Protocol
On-chain USDC payments via the x402 protocol
Billing & Units
Understand CU consumption and plan details

