Agent skill · software engineering · aiskillstore
nansen-mpp-payment
Pay-per-call access to the Nansen API via MPP (Tempo). Use when a user wants anonymous Nansen access without an API key and without managing their own Base/Solana wallet — they install the tempo CLI separately and call the API through `tempo request`.
Why this skill is useful
Adds specific commands and workflows for accessing the Nansen API via Tempo that the AI wouldn't reliably generate on its own.
What it needs
Requires tempo installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
MPP / Tempo The Nansen API supports three paid-access rails: API key, x402 (handled by nansen-cli), and MPP via Tempo (handled by the separate tempo CLI). This skill covers the third. nansen-cli does not sign MPP credentials. Use this skill when the user wants to call the Nansen API through tempo request because they already use tempo, want micropayments without managing wallet keys themselves, or don't want to fund a Base/Solana USDC wallet. For API-key auth, see nansen-wallet-manager. For x402 micropayment with a local wallet, see nansen-trading / nansen-wallet-manager. When to use this skill User says "MPP", "tempo", "Authorization: Payment", or "Payment-Receipt". User has no Nansen API key and doesn't want to set up a Base/Solana wallet. User is already paying for other APIs through tempo and wants Nansen on the same rail. One-time setup Calling the Nansen API tempo request handles the full MPP challenge/response: it sends the request, signs the Authorization: Payment credential when the API responds 402 + WWW-Authenticate: Payment ..., retries, and exposes the Payment-Receipt header on success. Endpoint paths and request shapes are the same as the rest of the Nansen API — run nansen schema <command> (no API key required) to look up the body shape, then call the matching /api/v1/... path through tempo request. Discovering paid endpoints Returns paymentProtocols: ["x402", "mpp"] (when MPP is enabled server-side) and the list of paid resources. How MPP differs from x402 x402 (nansen-cli native) MPP via tempo (this skill) --- --- --- Header sent on retry Payment-Signature: <base64> Authorization: Payment <credential> 402 challenge header Payment-Required: <base64> WWW-Authenticate: Payment ... …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/nansen-mpp-payment