nansen-agent-guide
Routing guide -- when to use `nansen agent` (AI research) vs direct CLI data commands. Use when deciding how to answer a user's…
Has SM been in this token for weeks, or did they just enter? Are they still buying?
$ npx -y skills add nansen-ai/nansen-cli --skill nansen-smart-money-trend --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/nansen-smart-money-trendContext preview
The summary Claude sees to decide when to auto-load this skill.
Has SM been in this token for weeks, or did they just enter? Are they still buying?
name: nansen-smart-money-trend
description: "Has SM been in this token for weeks, or did they just enter? Are they still buying?"
metadata:
openclaw:
requires:
bins:
- nansen
primaryEnv: NANSEN_API_KEY
install:
- kind: node
package: nansen-cli
bins: [nansen]
allowed-tools: Bash(nansen:*)Browser login requests `nansen:api` for API-key-equivalent account API permissions; existing OAuth/MCP `nansen:read` semantics and separate wallet authorization are unchanged.
Before any research command or loop, require an explicitly selected API key or saved browser session. Run `nansen auth status` first. Its cached/unverified metadata does not prove credential validity or unlocked storage. Cached access-token expiry alone does not mean the session is unusable: the CLI normally renews a selected session automatically during an already-authorized research task, without another consent request or a separate account check. Stop on anonymous selection, invalid authentication state, blocked or uncertain renewal/cleanup, or an actual authentication failure, including rejected or expired refresh authority. Follow the CLI error guidance; use the free `nansen account` check when troubleshooting calls for it. Do not unset a failed key, erase a session or switch to anonymous access to retry.
Use `nansen login` for fresh browser approval within the documented platform scope, or configure a conventional API key. `NANSEN_API_KEY` overrides the saved session. OpenClaw's optional `primaryEnv` mapping preserves configured API-key injection; it is not a required-key gate or proof of authentication. Normal credits and entitlements apply. Login does not purchase credits. Browser login is available in CLI 2.0.0 within the [macOS arm64 preview scope](https://github.com/nansen-ai/nansen-cli/blob/main/docs/browser-login.md#preview-platform-scope).
API keys and browser sessions use the same automatic x402 payment behavior: a supported HTTP 402 challenge can spend funds from the configured wallet under existing wallet authorization, payment policy and spending limits. Each call, including calls in loops, can incur a payment. Authentication, authorization and session-renewal failures never trigger payment; login verification and `nansen account` never pay automatically. Anonymous x402 remains available as a separate paid workflow requiring explicit user intent and payment setup. Do not run this research workflow anonymously or switch to anonymous access after authentication fails.
TOKEN=<address> CHAIN=ethereum nansen research smart-money netflow --chain $CHAIN --limit 200 # → filter by token_address; net_flow_1h_usd, net_flow_24h_usd, net_flow_7d_usd, net_flow_30d_usd nansen research token holders --token $TOKEN --chain $CHAIN --smart-money --limit 20 # → address_label, value_usd, balance_change_24h, balance_change_7d, balance_change_30d nansen research token flow-intelligence --token $TOKEN --chain $CHAIN # → smart_trader_net_flow_usd, whale_net_flow_usd, fund_net_flow_usd, fresh_wallets_net_flow_usd nansen research token dex-trades --token $TOKEN --chain $CHAIN --limit 50 # → block_timestamp, action, trader_address_label — find oldest SM-labeled BUY
1h/24h+ & 7d/30d+ = sustained accumulation. 24h+ & 7d− = fresh entry. 24h− & 7d+ = reducing. All negative = distribution.
Built by agents, for agents. Command-line interface for the Nansen API, designed for AI agents to research on-chain data, manage wallets, and trade through nansen trade. Use it for both analytics and execution: nansen research ...
Routing guide -- when to use `nansen agent` (AI research) vs direct CLI data commands. Use when deciding how to answer a user's…
Set up a local webhook server to receive Nansen smart alerts in real-time with HMAC signature verification and public tunneling.…
What tokens are whales dollar-cost averaging into? Jupiter DCA strategies by smart money and target token fundamentals.
What DeFi positions does a wallet hold? Protocol-by-protocol breakdown of assets, debts, and rewards across chains.
Is smart money exiting a token I hold? Net flow direction, seller breakdown by label, and recent SM trades.
What are crypto funds and VCs holding right now? Cross-chain fund portfolios and net accumulation signals.