Back to Details

nansen-mpp-payment

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

MPP / Tempo

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
.
Nansen API支持三种付费访问方式：API密钥、x402（由
nansen-cli
处理）以及通过Tempo实现的MPP（由独立的tempo CLI处理）。本技能介绍的是第三种方式。
nansen-cli
不会签署MPP凭证。当用户希望通过
tempo request
调用Nansen API时使用本技能，原因可能是他们已经在使用tempo、希望无需自行管理钱包密钥即可进行微支付，或者不想为Base/Solana USDC钱包充值。
如需了解API密钥认证方式，请查看
nansen-wallet-manager
。如需了解使用本地钱包的x402微支付方式，请查看
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.
  • 用户提及“MPP”、“tempo”、“Authorization: Payment”或“Payment-Receipt”时。
  • 用户没有Nansen API密钥且不想设置Base/Solana钱包时。
  • 用户已经通过tempo为其他API付费，希望将Nansen接入同一支付渠道时。

One-time setup

一次性设置

bash
undefined
bash
undefined

1. Install the tempo CLI

1. Install the tempo CLI

curl -fsSL https://tempo.xyz/install | bash
curl -fsSL https://tempo.xyz/install | bash

2. Log in (creates / unlocks the tempo wallet)

2. Log in (creates / unlocks the tempo wallet)

tempo wallet login
tempo wallet login

3. Fund it with USDC on the chain tempo selects for your environment

3. Fund it with USDC on the chain tempo selects for your environment

tempo wallet fund
tempo wallet fund

4. Confirm the wallet is ready

4. Confirm the wallet is ready

tempo wallet whoami
undefined
tempo wallet whoami
undefined

Calling the Nansen API

调用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.
bash
undefined
tempo request
会处理完整的MPP挑战/响应流程：发送请求，当API返回402 + 
WWW-Authenticate: Payment ...
时签署
Authorization: Payment
凭证，重试请求，并在成功时返回
Payment-Receipt
头信息。
bash
undefined

Smart Money netflow

Smart Money netflow

tempo request POST https://api.nansen.ai/api/v1/smart-money/netflow
--json '{"chains":["solana"],"pagination":{"page":1,"page_size":10}}'
tempo request POST https://api.nansen.ai/api/v1/smart-money/netflow
--json '{"chains":["solana"],"pagination":{"page":1,"page_size":10}}'

TGM holders

TGM holders

tempo request POST https://api.nansen.ai/api/v1/tgm/holders
--json '{"token_address":"EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v","chain":"solana"}'

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`.
tempo request POST https://api.nansen.ai/api/v1/tgm/holders
--json '{"token_address":"EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v","chain":"solana"}'

端点路径和请求格式与Nansen API的其他部分一致——运行`nansen schema <command>`（无需API密钥）即可查看请求体格式，然后通过`tempo request`调用对应的`/api/v1/...`路径。

Discovering paid endpoints

发现付费端点

bash
curl https://api.nansen.ai/.well-known/x402
Returns 
paymentProtocols: ["x402", "mpp"]
(when MPP is enabled server-side) and the list of paid resources.
bash
curl https://api.nansen.ai/.well-known/x402
返回内容包含
paymentProtocols: ["x402", "mpp"]
（当MPP在服务器端启用时）以及付费资源列表。

How MPP differs from x402

MPP与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 ...
Success header(none)
Payment-Receipt: <base64>
Walletlocal, Privy, or WalletConnect — managed by 
nansen-cli
tempo-managed (separate CLI)
ChainsBase USDC, Solana SPL USDC, X Layer USDT0Tempo's chain (mainnet 
USDC
in prod, moderato 
pathUSD
in dev)
nansen-cli code path
src/x402.js
auto-signs on 402		not handled — call via 
tempo request
directly
x402（nansen-cli原生支持）MPP via tempo（本技能）
重试时发送的头信息
Payment-Signature: <base64>
Authorization: Payment <credential>
402挑战头信息
Payment-Required: <base64>
WWW-Authenticate: Payment ...
成功响应头信息(无)
Payment-Receipt: <base64>
钱包本地钱包、Privy或WalletConnect —— 由
nansen-cli
管理		由tempo管理（独立CLI）
链Base USDC、Solana SPL USDC、X Layer USDT0Tempo指定的链（生产环境为主网
USDC
，开发环境为moderato 
pathUSD
）
nansen-cli代码路径
src/x402.js
会在402时自动签署		不处理——直接通过
tempo request
调用

Notes

注意事项

  • MPP is server-side opt-in. If 
    tempo request
    returns a 402 without 
    WWW-Authenticate: Payment
    , MPP isn't enabled for that endpoint/environment — fall back to an API key or x402.
  • Don't try to add 
    --mpp-*
    flags to 
    nansen-cli
    — the supported integration is "use tempo separately". If the user asks for tighter integration, point them at this skill and confirm the requirement before adding code.
  • Per-request price is the same as x402 (1 credit ≈ $0.001 with 10x markup, e.g. 1-credit endpoints cost $0.01).
  • MPP需要服务器端启用。如果
    tempo request
    返回402但未携带
    WWW-Authenticate: Payment
    头信息，则该端点/环境未启用MPP——请改用API密钥或x402方式。
  • 不要尝试给
    nansen-cli
    添加
    --mpp-*
    参数——支持的集成方式是“单独使用tempo”。如果用户要求更紧密的集成，请引导他们查看本技能，并在添加代码前确认需求。
  • 单次请求的价格与x402相同（1积分≈0.001美元，加价10倍后，例如1积分的端点费用为0.01美元）。

Source

参考来源