Nansen
Onchain analytics platform with wallet labeling and smart-money tracking, offering an API with key-based and x402 access.
- Sato Score82
- ChainsEthereum, Base +5
Nansen is a closed-source data tool by Nansen on Ethereum, Base, Solana and other chains, with last code activity on 2026-10-22 (Active). Latest release on 2026-10-22. Sato Score 82/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-23. How the score works →
See how to install Nansen →Last commit Oct 22, 2026 · Last release Oct 22, 2026 (v2.3.0) · ★ 139
Last news post Jun 4, 2026 on X
Listed from nansen.ai on 2026-06-08. Install: reproduced by Sato Hub on 2026-10-15. Evidence →
Next step
Watch Nansen
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on nansen-ai/nansen-cli before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
Nansen is an established onchain analytics platform that labels a large set of crypto wallets and surfaces smart-money flows, whale activity, and real-time alerts, with in-app trading. Its API offers direct HTTP access via API key or x402 micropayments; the x402 routes on api.nansen.ai (profiler, token god mode, smart money) are listed in the Coinbase x402 Bazaar and in the curated x402 catalog of Coinbase for Agents (https://docs.cdp.coinbase.com/coinbase-for-agents/overview), so an agent connected to a Coinbase account can pay for them from its USDC balance. Wallet-label counts and assets-tracked figures are as reported by Nansen and should not be treated as independently verified.
Sato Score
82/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 11/20
- Interface verifiability
- 8/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 15/15
- Independent verification
- 7/10
Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).
Sato Check
v2.3.0 · as of 2026-10-23- Does it take your key?
- No key read found
- Does your key leave?
- Not yet run
- Can it move funds on its own?
- Unknown
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
Evidence — listed vs checked · what the words mean
Listed from nansen.ai on 2026-06-08. Install: reproduced by Sato Hub on 2026-10-15.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Ethereum, Base, Solana, Arbitrum, Optimism, Polygon, Multichain | self-reported | nansen.ai | as of 2026-10-23 |
| Verification status | Self-Reported — not independently reviewed | self-reported | nansen.ai | as of 2026-10-23 |
| Recent activity | last release 2026-10-22 · last commit 2026-10-22 | observed | github.com/nansen-ai/nansen-cli | 2026-10-23 |
| Install works | reproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour | ✓ reproduced | docs.nansen.ai | 2026-10-15 |
| Website answers | answered (HTTP 200) | observed | nansen.ai | 2026-10-23 |
| Daily check record | 90 of 90 daily checks since 2026-07-25 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-22 |
| ERC-8004 registration | declared address not found in the registry | observed | — | 2026-10-23 |
| Takes your key | no private-key read found in what we read | traced | satohub.ai | 2026-10-23 |
| Key leaves the machine | not yet run with planted test keysthe sandbox lane has not run on this version | observed | satohub.ai | not dated |
| Moves funds on its own | unknown — could not read what it exposes | traced | satohub.ai | 2026-10-23 |
| Built by | Nansenconfidence 0.60 | self-reported | nansen.ai | as of 2026-06-25 |
| Deploys as | API, MCP server, npmconfidence 0.85 | self-reported | nansen.ai | as of 2026-06-25 |
| Works with | MCP, REST API, CLI, x402confidence 0.85 | self-reported | nansen.ai | as of 2026-06-25 |
| Sato Score | 82/100 (High)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-23 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — reproduced in a container Oct 15, 2026
Runtime: Node.js (nansen-cli, npm global package) + hosted MCP endpoint
npm install -g nansen-cli nansen <command> <subcommand> [options] — key commands: research, trade, agent, wallet, schema. MCP: npx -y mcp-remote https://mcp.nansen.ai/ra/mcp --header "NANSEN-API-KEY: <key>" --allow-http, or `claude mcp add --transport http nansen https://mcp.nansen.ai/ra/mcp --header "NANSEN-API-KEY: <key>"`
You supply: NANSEN_API_KEY (from https://app.nansen.ai/api?tab=api), Optional: NANSEN_WALLET_PASSWORD for x402 local wallet auth; PRIVY_APP_ID / PRIVY_APP_SECRET for Privy server-side wallets (custody-relevant if used)
claude mcp add --transport http satohub-nansen https://mcp.nansen.ai/ra/mcp
A remote server: your client connects to the project's endpoint. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.
Read from the project’s own docs as of 2026-10-15. What a deploy spec is →
Observed record — 90 daily checks since 2026-07-26
- Succeeded
- 90
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 37 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-23, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Skills that target this — 1, with disclosures
nansen-tradingskills.sh · nansen-ai
422 installsExecute DEX swaps on Solana or Base (including cross-chain bridges) and Hyperliquid perpetual trades. Use when buying or selling a token, getting a swap quote, executing a trade, or opening/closing/managing a perp position.
Disclosures describe what a skill declares and does; they are not safety verdicts. All skills →
Details
- Chains
- Ethereum, Base, Solana, Arbitrum, Optimism, Polygon, Multichain
- Agent types
- Data Provider
- Open source
- No
- Pricing
- Subscription; API key or x402 micropayments
- Deploys as
- API, MCP server, npm
- Works with
- MCP, REST API, CLI, x402
- Last checked
- 2026-10-23
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where Nansen fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are Onchain Agents?
Recent Activity
All news →Releases and posts from Nansen, pulled from its GitHub and X.
nansen-cli v2.3.0
Minor Changes #747 32a4ab2 Thanks @hulk-linus ! - Add feedback submit and receipt lookup with explicit submission IDs, account authentication, safe retries, and JSON or human output. Explain the agent preference rule in CLI guidance: ask before sending when the saved preference is off, unset or unavailable. Explain paused submissions: report the unavailable feature, stop repeated attempts, and pre
nansen-cli v2.2.0
Minor Changes #735 223acdd Thanks @kome12 ! - trade execute : non-gasless swaps now broadcast through the execution route that tracks the on-chain outcome server-side, instead of the deprecated /execute route. Set NANSEN_TRADING_EXECUTION_ROUTE=legacy to go back to the old route; any value other than standard or legacy is rejected rather than silently falling back. Three behaviours change for swap
nansen-cli v2.1.0
Minor Changes #728 c5ef96f Thanks @gulshngill ! - Drop support for Node.js 20 (EOL since April 2026). The minimum supported version is now Node.js 22: engines.node is >=22.0.0 , CI tests on Node 22 and 24, and nansen doctor reports Node 20 as below the required version. #584 435ae1a Thanks @ygd58 ! - nansen wallet list now prints the standard JSON envelope on stdout, {"success":true,"data":{"walle
You track Smart Money here. Now trade here too. Trade Where You Research - Hyperliquid Perps. Jun 9. 🐱 https://t.co/ZhTWkp43rV
This @HyperliquidX whale is sitting on ~$40M unrealized on a single $HYPE long. Entry at $38.68, +373% ROI. They've paid $2.83M in funding to hold this position and they're still holding. Over the las
This @HyperliquidX whale is sitting on ~$40M unrealized on a single $HYPE long. Entry at $38.68, +373% ROI. They've paid $2.83M in funding to hold this position and they're still holding. Over the last 15 days they've been moving $2-5M in USDC in and out of Coinbase repeatedly - managing around the position while keeping the core long intact. The same wallet has been liquidated before. Now it's si
Listing History
Recorded changes to Nansen's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Oct 22, 2026New release published
- Oct 15, 2026Verified: deploy spec
- Oct 9, 2026New release published
- Oct 8, 2026Sato Score tier: Medium → HighScore 47 → 74.
- Oct 8, 20263 releases trackedShowing the 2 most recent. Full release history is retained in the listing record.
- Sep 23, 2026Edited: description long, tags
- Jul 26, 2026Sato Hub began tracking this listing
- Jun 25, 2026Enriched: creator name, marketplace notes
- Jun 25, 2026Auto-enriched: supported integrations, deployment options, has pricing
Compared with
Appears in
- Onchain trading tools on Base, scored →
- x402 payment tools on Base, scored →
- x402-ready tools, scored →
- Onchain trading tools on Solana, scored →
- Npm-installable crypto agent tools, scored →
- x402 payment tools on Solana, scored →
- Payment tools for agents, scored →
- x402 endpoints checked for a payment-required answer →
- x402 facilitators on Base →
- x402: agent payments over HTTP →
- Onchain agents on Base →
- Onchain agents on Solana →
Related Resources
Agent Payments Protocol (AP2)
ActiveOpen protocol from Google for secure agent-led payments across traditional and crypto rails, with a crypto-native x402 extension built with Coinbase, Ethereum Foundation, and MetaMask.
Zerion
ActiveWallet and DeFi data provider offering portfolio, positions, transactions, PnL, and prices across many chains, with an agent-accessible API.
Bankr
ActiveCrypto execution layer and cross-chain wallet that lets agents and users trade, bridge, and manage assets via natural language, plus a skills marketplace and an x402 cloud for spinning up pay-per-call agent endpoints.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Nansen
- Is Nansen open source?
- No. Nansen is closed source as of 2026-10-23.
- Which chains does Nansen support?
- Nansen lists support for Ethereum, Base, Solana, Arbitrum, Optimism, Polygon, Multichain as of 2026-10-23.
- Is Nansen still maintained?
- The most recent code activity Sato Hub observed was on 2026-10-22 (last commit 2026-10-22, last release 2026-10-22), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run Nansen?
- Node.js (nansen-cli, npm global package) + hosted MCP endpoint. Install: npm install -g nansen-cli. Entry: nansen <command> <subcommand> [options] — key commands: research, trade, agent, wallet, schema. MCP: npx -y mcp-remote https://mcp.nansen.ai/ra/mcp --header "NANSEN-API-KEY: <key>" --allow-http, or `claude mcp add --transport http nansen https://mcp.nansen.ai/ra/mcp --header "NANSEN-API-KEY: <key>"`. Sato Hub reproduced this install in a container on 2026-10-15. It runs as an MCP server (hosted: https://mcp.nansen.ai/ra/mcp (via mcp-remote or native HTTP transport)).
- Is Nansen verified on Sato Hub?
- Sato Hub holds one earned check for Nansen: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 82 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Nansen — Sato Hub." Sato Hub, updated 2026-10-23, accessed 2026-10-24. https://satohub.ai/resources/nansenData last refreshed 2026-10-23; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.