← Protocols
Nansen
Analytics·EVM · Solana · Bitcoin · Multi-chain

Nansen

01Description

Wallet labels and onchain analytics — Smart Money tracking, entity tagging on hundreds of millions of addresses, token god-mode, and wallet profilers across 18+ chains.

02Best for
  • 01wallet labels (CEX, fund, smart money)
  • 02Smart Money flows
  • 03token holder analytics
  • 04alpha signals for trading UIs
  • 05wallet profile pages
04Environment variables
VariableScopeDescription
NANSEN_API_KEYServerNansen API key from the Nansen dashboard. Server-only.
05Prompt snippet
Use Nansen for wallet labels and smart-money analytics. From the server, fetch `https://api.nansen.ai/api/beta/{path}` with header `apiKey: $NANSEN_API_KEY`. Common endpoints: `POST /address/labels` for entity tags, `POST /smart-money/inflows` for fund flows, `POST /profiler/{address}/balances` for portfolio snapshots, and `POST /tgm/{tokenAddress}/holders` for token god-mode. Cache responses aggressively — Nansen bills per call ($0.01–$0.05 each) and rate-limits at 20 req/s, 500 req/min.
06Gotchas
  • Pay-per-call pricing ($0.01 Basic, $0.05 Advanced) means an unbounded loop can rack up real money fast — always cap and cache.
  • Rate limits are 20 req/s and 500 req/min globally per key; bursts above this 429 immediately.
  • Labels are proprietary and licensed — re-exposing raw label data in your own API may violate ToS; check before reselling.
  • Chain coverage is uneven: Smart Money signals are richest on Ethereum/Solana, sparser on long-tail L2s.
  • Some endpoints require the Advanced tier — a 403 doesn't always mean wrong key, it can mean wrong plan.
07Alternatives