About nansen-general-search
A command-line skill for searching Nansen token and entity data, with chain, result-count, and output-field filters. It is intended for researchers using an explicitly authenticated Nansen session or API key.
Key features
- 01Search tokens and entities
- 02Filter by chain
- 03Set result limits
- 04Choose output fields
- 05Case-insensitive queries
Use cases
- 01Find tokens by name or symbol
- 02Search for entities such as Vitalik
- 03Narrow results to a chain
- 04Return selected fields for research
MCP support
The skill uses Nansen CLI research commands; it does not describe an MCP integration.
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/nansen-general-searchin Claude Code to confirm it loaded.
Details
From the project READMEAuthentication
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.
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.
Search
nansen research search "jupiter" --type token
nansen research search "Vitalik" --type entity --limit 5
nansen research search "bonk" --chain solana --fields address,name,symbol,chain
| Flag | Purpose |
|---|---|
--type | token or entity |
--chain | Filter by chain |
--limit | Number of results (default 25, max 50) |
--fields | Select specific output fields |
Case-insensitive. Does NOT match by address — use profiler labels for address lookup.