Skip to main content
The Machine Payments Protocol (MPP) is the second way to pay. The payment is a USDC.e transfer on the Tempo chain. The mppx client library reads the challenge and builds the credential you send on the retry.

How it works

A valid unpaid request to a paid route also returns an MPP challenge beside the x402 one, in a www-authenticate: Payment header. The challenge names the method (tempo), the intent (charge), the amount and the address to pay. A client signs a Tempo charge, retries with the credential, and the server settles it on-chain.

Use mppx

The same EVM address holds your Base USDC and your Tempo USDC.e, so one key covers both.

When to pick MPP over x402

Use whichever rail your funds are on. Hold USDC.e on Tempo, or already pay other MPP APIs? Use MPP. Hold USDC on Solana or Base? Use x402.

Pricing

The price is the same on every rail. See Pricing.