Skip to main content
Call fixed-price Xquik operations without an account or subscription. Pay per request with Tempo (USDC) using the mppx SDK.

Step 1: install the SDK

The mppx package provides both client and server utilities. You only need the client. viem manages the wallet account.

Step 2: set up a Tempo wallet

You need a Tempo wallet funded with USDC, plus its raw hex private key for the mppx client. Path A. CLI only. Recommended for agents.
Fund the account’s address with USDC on Tempo, then copy the exported key into TEMPO_PRIVATE_KEY. Path B. Web wallet as a USDC source. Use wallet.tempo.xyz/welcome as a hosted UI to buy & send USDC. Run mppx account create to create a local account and copy its address. Send USDC from the web wallet to that address. Then run mppx account export to get the hex key. You cannot import the web wallet into mppx. It is a funding source, not a key source.
Warning. Never commit your private key to version control. Load it from an environment variable.

Step 3: make a charge request

Look up a single tweet. The SDK intercepts 402 responses, pays via Tempo, and retries automatically.
Mppx.create() patches the global fetch function. When a direct MPP request returns 402 with a WWW-Authenticate: Payment header, the SDK pays the requested amount and retransmits the request with an Authorization: Payment credential. Every response after accepted payment includes a Payment-Receipt header confirming settlement.

Step 4: raw HTTP flow without the SDK

Without the mppx SDK, implement the protocol yourself. Step 1. Request the endpoint.
Step 2. Receive the 402 challenge.
The request parameter is a base64url-encoded JSON object containing the amount, currency, and recipient address. The application/problem+json body also includes an optional payment_options.guest_wallet.create_checkout action. It does not replace the MPP header. The failed request creates no checkout. Ignore it when completing MPP. Use it only after a user explicitly chooses and confirms a USD 10 to 250 guest wallet. Step 3. Pay and retry. After completing the Tempo payment, retry the request with the payment credential:
The Authorization: Payment value is a base64url-encoded JSON object containing the original challenge and your payment proof. Step 4. Receive the response and receipt.
The Payment-Receipt header confirms settlement. Check the HTTP status and response body separately because accepted payments also include a receipt on non-2xx responses.

Next steps

  • MPP overview: direct MPP operations, pricing, and protocol details.
  • Guest wallets: Prepay the eligible reads with an accountless API key.
  • Get tweet: Full endpoint reference for tweet lookups.
  • Get user: Full endpoint reference for user lookups.