MPP Tempo
MPP issues a payment challenge through the standard Authorization flow. The client answers with a Payment credential, and AgentPay verifies and charges it before forwarding the request.
- URL segment
mpp-tempo- Payment header
Authorization- Availability
- Paid plans
- Best for
- Clients that support MPP credentials and want token payments on Tempo mainnet.
Endpoint URL
https://agent-proxy.alchemy.com/v1/mpp-tempo/{projectId}/{endpointSlug}/{path}Setup
- Enable MPP Tempo in the dashboard.
- Enter the recipient wallet address on Tempo mainnet.
- Enter the contract address of the token clients pay with.
- Set the price per request in token units.
- Save the channel and send an unpaid request to confirm the challenge is returned.
Request flow
- The client calls the mpp-tempo URL without a payment credential.
- AgentPay returns HTTP 402 with an MPP challenge.
- The client obtains or creates a matching Payment credential.
- The client retries with the credential in the
Authorizationheader. - AgentPay verifies and charges the credential, then forwards the request to your backend.
Notes
- Prices for MPP channels are entered as decimal token amounts.
- The recipient and token address must match the network your clients use.
- Invalid credentials are rejected before your backend receives the request.