
Nansen General Search
- 363 installs
- 127 repo stars
- Updated August 4, 2026
- nansen-ai/nansen-cli
nansen-general-search is a Claude Code skill that runs Nansen CLI research search commands so developers who investigate crypto wallets and tokens can resolve addresses, symbols, and entity records from names.
About
nansen-general-search is an agent skill for the nansen-cli Node package that executes nansen research search with --type token or entity, optional --chain filters, and --fields selectors such as address, name, symbol, and chain. Developers reach for it when a token ticker or wallet label must become a canonical on-chain address before deeper Nansen analytics. The skill requires NANSEN_API_KEY in the environment and the nansen binary on PATH, with Bash scoped to nansen:* commands only.
- On-chain search
- Entity discovery
- Nansen CLI
- Cross-chain lookup
Nansen General Search by the numbers
- 363 all-time installs (skills.sh)
- +3 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #41 of 479 Web3 & Blockchain skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/nansen-ai/nansen-cli --skill nansen-general-searchAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 363 |
|---|---|
| repo stars | ★ 127 |
| Last updated | August 4, 2026 |
| Repository | nansen-ai/nansen-cli ↗ |
How do you find a token contract address by name?
Run broad Nansen CLI searches across wallets, tokens, labels, and transactions to discover entities and flows during early crypto research.
Who is it for?
Developers and analysts building crypto research agents who already have a Nansen API key and need name-to-address resolution.
Skip if: Teams without a Nansen subscription or workflows that only need price charts without on-chain entity resolution.
When should I use this skill?
User has a token name, ticker, or entity label and needs the full contract address or Nansen entity record.
What you get
Resolved token or entity addresses, symbols, chains, and labeled metadata rows from Nansen search output.
- token address rows
- entity match list
- chain-filtered search output
By the numbers
- Installs nansen binary via nansen-cli npm package
- Documents example --limit 5 for entity search results
Files
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.
Related skills
How it compares
Pick nansen-general-search over nansen-token-screener when the task starts from a known name rather than trending-token discovery.
FAQ
What environment does nansen-general-search need?
nansen-general-search requires NANSEN_API_KEY set in the environment and the nansen binary installed from the nansen-cli npm package. Bash access is limited to nansen:* command prefixes.
Which search types does Nansen general search support?
nansen-general-search uses nansen research search with --type token for contract lookup or --type entity for labeled wallets and organizations. Optional --chain and --limit flags narrow results.