--- name: api.nansen.ai description: api.nansen.ai provides on-chain blockchain analytics via a REST API, covering smart-money wallet tracking, token holder analysis, fund flow tracing, DEX and perpetual trade monitoring, and prediction market data. It draws on Nansen's labeled wallet database to surface activity from identified high-signal traders and entities. All endpoints return historical or snapshot data — there is no real-time streaming or order book access. host: api.nansen.ai --- # api.nansen.ai Nansen's API serves agents and applications that need on-chain intelligence beyond raw blockchain data — specifically, data enriched with wallet labels (smart money, institutions, known entities). It is oriented toward research, due diligence, and signal generation workflows rather than trade execution. Its primary differentiator is the labeled-wallet layer applied across token holders, DEX trades, perpetual trades, and fund flows. It covers multiple chains and asset classes including fungible tokens and prediction markets. ## When to use this host Use api.nansen.ai when an agent requires on-chain analytics enriched with wallet labels — specifically smart-money tracking, holder quality assessment, fund flow tracing, or prediction market intelligence. It is the right choice for due diligence on tokens, wallet profiling, and detecting high-signal trader activity across DEX spot and perpetual markets. Do not use it for real-time price feeds, OHLCV candles, or order book data — use a dedicated market data provider (e.g., CoinGecko, Binance, or a DEX quote API) instead. Do not use it for trade execution or swap routing — use a DEX aggregator API instead. It does not support real-time streaming or websocket feeds; all endpoints return snapshots or paginated historical records. CEX activity and off-chain data are outside its scope entirely. ## Capabilities ### Token Discovery and Metadata Resolve token identities, retrieve full token profiles, and screen tokens by on-chain metrics to build a foundational understanding of any asset before deeper analysis. - **`search-nansen-tokens-and-entities`** — Searches Nansen's blockchain dataset by name, symbol, contract address, or entity name and returns matching tokens and entities with price, volume, market cap, and rank. - **`fetch-tgm-token-information`** — Returns comprehensive token metadata, market metrics (market cap, FDV), and spot trading activity (volume, buys/sells, unique traders, liquidity, holders) for a given token and date range from Nansen's onchain analytics. - **`search-nansen-token-screener`** — Searches, filters, and ranks crypto tokens across chains using Nansen on-chain metrics and customizable screening criteria via a POST request. ### Token Holder Analysis Identify who holds a token, at what concentration, and with what inflow/outflow history, including filtering by smart-money or institutional labels. - **`fetch-token-holders`** — Returns a paginated list of on-chain token holders with balances, flow metrics, ownership percentages, and labeled entity names for a given token address and chain. - **`fetch-who-bought-sold`** — Returns on-chain wallet addresses that bought or sold a specified token or collection over a given time window, sourced from Nansen blockchain analytics. ### Smart Money Activity Track what labeled high-signal wallets are holding, buying, and trading across spot DEX and perpetual markets on supported chains. - **`fetch-smart-money-holdings`** — Returns token holdings and balances for Nansen-identified smart-money wallets on a specified blockchain, including USD value, holder count, market cap, and sector tags. - **`fetch-smart-money-dex-trades`** — Returns recent DEX trades executed by smart-money wallets on supported blockchains, including token addresses, amounts, symbols, market caps, and USD trade values. - **`fetch-smart-money-perp-trades`** — Returns a paginated list of smart-money perpetual trades across chains, including trader labels, addresses, token, side, action, position size, USD value, price, and transaction hash. ### Fund Flow and Transfer Tracing Trace on-chain capital movement for wallets, tokens, and protocols — including raw transfer records, aggregated flow maps, and multi-chain flow intelligence for risk and counterparty analysis. - **`fetch-tgm-transfers`** — Retrieves on-chain token transfer (TGM) records from Nansen across supported networks for analytics, tracing, and transaction monitoring. - **`fetch-nansen-flowmap`** — Returns aggregated on-chain fund flow analytics for wallets, tokens, and protocols across supported blockchains via Nansen's FlowMap API. - **`fetch-nansen-flow-intelligence`** — Traces token and wallet movements across multiple chains to identify fund-flow sources, sinks, and on-chain risk signals in real time. ### Wallet Portfolio Snapshot Retrieve the current token holdings and USD valuations for a specific wallet address on a supported chain. - **`fetch-address-current-balance`** — Returns current native and token balances with USD valuations for a wallet address on a specified blockchain, paginated by token holding. ### Prediction Market Intelligence Explore prediction market categories, retrieve trade history for specific markets or wallets, and identify top position holders for concentration and sentiment analysis. - **`fetch-prediction-market-categories`** — Returns paginated prediction market category analytics from Nansen, including active markets, open interest, volume, and top market details per category. - **`fetch-prediction-market-trades`** — Returns paginated trade records for a specific prediction market, filtered by date range and ordered by a specified field. - **`fetch-prediction-market-trades-by-address`** — Returns prediction market trades for a given wallet address within an optional date range, with sorting and pagination support. - **`fetch-prediction-market-top-holders`** — Returns the top holders for a specified prediction market from Nansen's on-chain analytics data. ## Workflows ### Token Due Diligence Pipeline *Use when an agent needs to build a comprehensive profile of a token — from identity resolution through holder quality and smart-money interest.* 1. **`search-nansen-tokens-and-entities`** — Resolve the token name or symbol to a verified contract address and chain. 2. **`fetch-tgm-token-information`** — Retrieve full token metadata, market cap, FDV, trading volume, and spot activity for the resolved contract. 3. **`fetch-token-holders`** — Identify top holders, filter for smart-money or institutional labels, and assess ownership concentration. 4. **`fetch-smart-money-holdings`** — Check whether the token appears in smart-money wallet holdings and review 24h balance changes and sector tags. 5. **`fetch-who-bought-sold`** — Identify which wallets bought or sold the token recently to assess directional conviction from labeled participants. ### Smart Money Signal Aggregation *Use when an agent needs to surface tokens or positions that smart-money wallets are actively trading across both spot and derivatives markets.* 1. **`fetch-smart-money-dex-trades`** — Pull recent DEX trades by smart-money wallets on the target chain to identify tokens being accumulated or distributed. 2. **`fetch-smart-money-perp-trades`** — Cross-reference with perpetual trade activity from the same labeled wallets to detect directional conviction or hedging behavior. 3. **`fetch-smart-money-holdings`** — Confirm current holdings to distinguish short-term trades from sustained positions. ### Wallet Fund Flow Investigation *Use when an agent needs to trace the origin or destination of funds for a specific wallet address, such as for risk assessment or counterparty identification.* 1. **`fetch-address-current-balance`** — Snapshot the wallet's current token holdings and USD values to establish its present state. 2. **`fetch-tgm-transfers`** — Retrieve historical transfer records for the address to map inbound and outbound token movements. 3. **`fetch-nansen-flow-intelligence`** — Apply multi-chain flow intelligence to identify counterparties, detect risk signals, and trace fund sources and sinks. ### Token Screening to Holder Drill-Down *Use when an agent needs to rank tokens by on-chain criteria and then investigate the holder base of top candidates.* 1. **`search-nansen-token-screener`** — Screen and rank tokens across chains using smart money activity, holder counts, or volume filters. 2. **`fetch-token-holders`** — For top-ranked tokens, retrieve paginated holder lists filtered by label type or ownership threshold. 3. **`fetch-who-bought-sold`** — Identify recent buyers and sellers of the shortlisted tokens to assess momentum and wallet quality. ### Prediction Market Research *Use when an agent needs to evaluate a prediction market category, find active markets, and assess participant concentration.* 1. **`fetch-prediction-market-categories`** — Survey available categories to identify markets with high volume, open interest, or trader activity. 2. **`fetch-prediction-market-trades`** — Retrieve trade history for a specific market ID identified in the category overview. 3. **`fetch-prediction-market-top-holders`** — Identify the largest position holders in the market to assess concentration and potential price impact. ## Skill reference ### `search-nansen-token-screener` **Nansen Token Screener** — Searches, filters, and ranks crypto tokens across chains using Nansen on-chain metrics and customizable screening criteria via a POST request. *Use when:* Use when an agent needs to screen or rank crypto tokens by on-chain metrics such as smart money activity, holder counts, or trading volume across multiple chains. *Not for:* Do not use for real-time price feeds or order book data; use a dedicated market data or DEX quote API instead. Not suitable for NFT screening. **Inputs:** - `body` (object, required) — POST body containing token screening filters and ranking criteria. Exact field structure not specified in the available schema; refer to Nansen API documentation for supported filter parameters. **Returns:** Returns a list of tokens ranked by the specified on-chain metric, with token metadata and Nansen analytics data per token. **Example:** `{"chains": ["ethereum"], "sort_by": "smart_money_inflow", "limit": 20}` --- ### `fetch-who-bought-sold` **Who Bought & Sold** — Returns on-chain wallet addresses that bought or sold a specified token or collection over a given time window, sourced from Nansen blockchain analytics. *Use when:* Use when an agent needs to identify which wallets were buyers or sellers of a specific token or NFT collection during a defined time period, for on-chain activity analysis or wallet profiling. *Not for:* Do not use for real-time price feeds or swap quotes; use a DEX quote API instead. Not suitable for portfolio balance lookups or token metadata queries. **Inputs:** - `asset` (string, required) — The token contract address or collection identifier to query buyer/seller activity for. **Returns:** Returns arrays of buyer and seller wallet addresses with on-chain activity details for the specified token or collection over the queried time window. **Example:** `{"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"}` --- ### `fetch-tgm-transfers` **Nansen TGM Transfers** — Retrieves on-chain token transfer (TGM) records from Nansen across supported networks for analytics, tracing, and transaction monitoring. *Use when:* Use when an agent needs historical or recent on-chain token transfer records for a given address or set of addresses, such as for tracing fund flows, auditing transactions, or building transfer analytics dashboards. *Not for:* Do not use for real-time streaming of transfer events; this is a single-shot query returning historical records. Not suitable for non-transfer on-chain activity such as contract calls or NFT mints. **Inputs:** - `asset` (string, required) — ERC-20 contract address of the payment asset used to settle the x402 paywall fee (USDC on Base). - `payTo` (string, required) — Wallet address to which the paywall fee is sent. - `amount` (string, required) — Paywall fee amount in atomic units of the payment asset (e.g., 10000 = 0.01 USDC with 6 decimals). - `scheme` (string, required) — Payment scheme; must be 'exact' for this endpoint. - `network` (string, required) — CAIP-2 network identifier on which the payment is made. - `maxTimeoutSeconds` (integer, required) — Maximum number of seconds the payment authorization is valid before expiry. **Returns:** Returns an array of on-chain token transfer records with sender, receiver, token, amount, and network metadata for the queried scope. **Example:** `{"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913", "payTo": "0x93053f1e7A5eFEDa532Fe69CbbE43cBEc3A0F13f", "amount": "10000", "scheme": "exact", "network": "eip155:8453", "maxTimeoutSeconds": 300}` --- ### `fetch-token-holders` **Token Holder Explorer** — Returns a paginated list of on-chain token holders with balances, flow metrics, ownership percentages, and labeled entity names for a given token address and chain. *Use when:* Use when an agent needs to identify top holders of a specific token, filter by value or ownership thresholds, or detect smart money / institutional holders by label for a given chain and token address. *Not for:* Do not use for real-time price feeds or swap quotes; use a DEX quote API instead. Not suitable for retrieving wallet transaction history — this returns holder snapshots, not transaction logs. **Inputs:** - `chain` (string, required) — Blockchain network to query (e.g. 'solana', 'ethereum'). - `token_address` (string, required) — On-chain mint or contract address of the token to query holders for. - `label_type` (string) — Holder label filter category (e.g. 'all_holders'). - `filters` (object) — Optional filter object with sub-fields: value_usd.min (minimum USD value), token_amount.min (minimum token balance), ownership_percentage.min (minimum ownership share), and include_smart_money_labels (array of label strings to include). - `order_by` (array) — Array of sort criteria for the returned holder list. - `pagination` (object) — Pagination control object (e.g. page and per_page fields). - `premium_labels` (boolean) — When true, returns enriched Nansen entity labels for holder addresses. - `aggregate_by_entity` (boolean) — When true, aggregates balances across addresses belonging to the same entity. **Returns:** Returns a data array of 10 holder records per page with address labels (e.g. 'Binance: Deposits', 'Pudgy Penguins: Liquidity'), token balances, USD values, ownership percentages, and 24h/7d/30d balance changes, plus pagination metadata. **Example:** `{"chain":"solana","token_address":"2zMMhcVQEXDtdE6vsFS7S7D5oUodfJHE8vd1gnBouauv","label_type":"all_holders","filters":{"value_usd":{"min":10000},"token_amount":{"min":1000},"ownership_percentage":{"min":0.01},"include_smart_money_labels":["30D Smart Trader","Fund"]},"order_by":[],"pagination":{},"premium_labels":true,"aggregate_by_entity":false}` --- ### `fetch-smart-money-holdings` **Smart Money Holdings** — Returns token holdings and balances for Nansen-identified smart-money wallets on a specified blockchain, including USD value, holder count, market cap, and sector tags. *Use when:* Use when an agent needs to identify which tokens smart-money wallets are holding on a given chain, including concentration metrics, 24h balance changes, and sector classifications for those tokens. *Not for:* Do not use for individual wallet-level portfolio lookups or transaction history; this aggregates holdings across smart-money wallets, not per-address data. **Inputs:** - `chains` (array, required) — List of blockchain names to filter holdings by. Each element is a chain identifier string. **Returns:** Returns a data array where each element describes one token held by smart-money wallets, including chain, address, symbol, sectors, total USD value, 24h balance change, holder count, share of holdings, token age, and market cap. **Example:** `{"chains": ["ethereum"]}` --- ### `fetch-smart-money-dex-trades` **Smart Money DEX Trades** — Returns recent DEX trades executed by smart-money wallets on supported blockchains, including token addresses, amounts, symbols, market caps, and USD trade values. *Use when:* Use when an agent needs to identify or monitor DEX trading activity from smart-money wallets on a specific chain, such as surfacing token buys/sells by labeled high-signal traders. *Not for:* Do not use for non-DEX on-chain activity (e.g., transfers, staking, lending); use a general transaction or DeFi activity endpoint instead. Not suitable for real-time streaming — this is a snapshot query. **Inputs:** - `chains` (array, required) — List of blockchain identifiers to filter trades by. At least one chain must be specified. **Returns:** Returns a data array of smart-money DEX trades, each with chain, timestamp, transaction hash, trader address and label, bought/sold token addresses and symbols, amounts, token ages, market caps, and USD trade value. **Example:** `{"chains": ["solana"]}` --- ### `fetch-address-current-balance` **Address Balance Snapshot** — Returns current native and token balances with USD valuations for a wallet address on a specified blockchain, paginated by token holding. *Use when:* Use when an agent needs a snapshot of all token holdings and their current USD values for a given wallet address on a supported chain such as Solana. *Not for:* Do not use for historical balance lookups or time-series portfolio tracking; this endpoint returns only the current balance state. **Inputs:** - `chain` (string, required) — Blockchain identifier for the wallet address (e.g. 'solana'). - `address` (string, required) — Wallet address to query balances for on the specified chain. **Returns:** Returns a paginated data array where each entry contains the token address, symbol, name, held amount, USD price, and total USD value for every token in the queried wallet. **Example:** `{"chain": "solana", "address": "DevFFyNWxZPtYLpEjzUnN1PFc9Po6PH7eZCi9f3tTkTw"}` --- ### `fetch-nansen-flowmap` **Nansen FlowMap** — Returns aggregated on-chain fund flow analytics for wallets, tokens, and protocols across supported blockchains via Nansen's FlowMap API. *Use when:* Use when an agent needs to analyze on-chain capital movement patterns — such as fund inflows/outflows for a wallet, token, or protocol — across multiple blockchains. *Not for:* Do not use for real-time price feeds or order book data; use a market data API instead. Not suitable for off-chain or CEX fund flow analysis. **Returns:** Returns aggregated on-chain fund flow data for the queried wallets, tokens, or protocols across supported blockchains. **Example:** `{"method":"POST","url":"https://api.nansen.ai/api/v1/tgm/flows","headers":{"Content-Type":"application/json"}}` --- ### `fetch-nansen-flow-intelligence` **Nansen Flow Intelligence** — Traces token and wallet movements across multiple chains to identify fund-flow sources, sinks, and on-chain risk signals in real time. *Use when:* Use when an agent needs to analyze on-chain fund flows for a token or wallet address to detect movement patterns, identify counterparties, or assess on-chain risk across multiple chains. *Not for:* Do not use for off-chain transaction data or CEX fund flows; this endpoint covers on-chain multi-chain activity only. Not suitable for historical price lookups — use a market data API instead. **Returns:** Returns multi-chain fund-flow analysis tracing token and wallet movements with sources, sinks, and on-chain risk signals. **Example:** `{"method":"POST","url":"https://api.nansen.ai/api/v1/tgm/flow-intelligence","headers":{"Content-Type":"application/json"}}` --- ### `fetch-smart-money-perp-trades` **Smart Money Perp Trades** — Returns a paginated list of smart-money perpetual trades across chains, including trader labels, addresses, token, side, action, position size, USD value, price, and transaction hash. *Use when:* Use when an agent needs to identify recent perpetual trading activity by labeled smart-money wallets, filtered by token, trade side, order type, action, or USD value range. *Not for:* Do not use for spot trading activity or token transfer analysis; use a spot trades or token flow endpoint instead. Not suitable for real-time streaming — this is a paginated snapshot query. **Inputs:** - `filters` (object) — Object containing filter criteria for the query. Supported sub-fields: side (e.g. 'Long'), type (e.g. 'Limit'), action (e.g. 'Buy - Add Long'), value_usd (object with min and max numeric bounds), token_symbol (e.g. 'BTC'). - `order_by` (array) — Array of ordering criteria for the results. - `pagination` (object) — Pagination control object (e.g. page, per_page). - `premium_labels` (boolean) — When true, includes premium trader label tags in results. - `only_new_positions` (boolean) — When true, attempts to filter results to newly opened positions only. **Returns:** Returns a data array of up to 10 smart-money BTC Long Limit trades per page, each with trader label, address, token amount, USD value, price, action, timestamp, and transaction hash, plus pagination metadata. **Example:** `{"filters":{"side":"Long","type":"Limit","action":"Buy - Add Long","value_usd":{"min":1000,"max":10000},"token_symbol":"BTC"},"order_by":[],"pagination":{},"premium_labels":true,"only_new_positions":true}` --- ### `fetch-prediction-market-trades-by-address` **Prediction Market Trades Lookup** — Returns prediction market trades for a given wallet address within an optional date range, with sorting and pagination support. *Use when:* Use when an agent needs to retrieve historical prediction market trade activity for a specific wallet address, optionally filtered by date range and ordered by a specified field. *Not for:* Do not use for real-time streaming trade feeds or for querying trades across multiple addresses in bulk; this endpoint accepts a single address per request. **Inputs:** - `address` (string, required) — Wallet address whose prediction market trades should be retrieved. - `date` (object) — Optional date range filter with 'from' and 'to' ISO 8601 timestamp fields. - `order_by` (array) — Array of sort directives, each with 'field' (e.g. 'timestamp') and 'direction' ('ASC' or 'DESC'). - `pagination` (object) — Pagination control with 'limit' (max records per page) and 'offset' (number of records to skip). **Returns:** Returns a pagination object (page, per_page, is_last_page) and a data array of prediction market trades for the queried address, which may be empty if no trades exist. **Example:** `{"address": "0x1234567890abcdef1234567890abcdef12345678", "date": {"from": "2024-01-01T00:00:00Z", "to": "2024-12-31T23:59:59Z"}, "order_by": [{"field": "timestamp", "direction": "DESC"}], "pagination": {"limit": 50, "offset": 0}}` --- ### `fetch-prediction-market-categories` **Prediction Market Categories** — Returns paginated prediction market category analytics from Nansen, including active markets, open interest, volume, and top market details per category. *Use when:* Use when an agent needs an overview of prediction market activity broken down by category (e.g. Politics, Sports, Crypto, Elections) including 24h/1wk volume, open interest, trader counts, and the top market question per category. *Not for:* Do not use for individual market details or order book data; use a market-specific endpoint instead. Not suitable for real-time streaming price feeds — this is a paginated snapshot. **Inputs:** - `pagination` (object) — Pagination control object specifying which page of results to return and how many results per page. - `pagination.page` (integer) — Page number to retrieve, starting at 1. - `pagination.per_page` (integer) — Number of category records to return per page. **Returns:** Returns a pagination object and a data array of up to 10 category records, each with active market count, open interest, 24h/1wk volume, 24h trader count, and the top market ID, question, and 24h volume. **Example:** `{"pagination": {"page": 1, "per_page": 10}}` --- ### `fetch-prediction-market-trades` **Prediction Market Trades** — Returns paginated trade records for a specific prediction market, filtered by date range and ordered by a specified field. *Use when:* Use when an agent needs to retrieve historical trade activity for a known prediction market ID, optionally scoped to a date range and sorted by timestamp or another field. *Not for:* Do not use for listing available prediction markets or fetching market metadata; this endpoint only returns trade records for a market whose ID is already known. **Inputs:** - `market_id` (string, required) — The unique identifier of the prediction market whose trades should be retrieved. - `date` (object) — Object with 'from' and 'to' ISO 8601 datetime strings defining the inclusive date range for filtering trades. - `order_by` (array) — Array of ordering objects, each with a 'field' (e.g. 'timestamp') and 'direction' ('ASC' or 'DESC'). - `pagination` (object) — Object with 'limit' (integer, max records per page) and 'cursor' (opaque string for cursor-based pagination). **Returns:** Returns a pagination object (page, per_page, is_last_page) and a data array of trade records; data may be empty if no trades exist for the given market and date range. **Example:** `{"market_id": "654412", "date": {"from": "2024-01-01T00:00:00Z", "to": "2024-12-31T23:59:59Z"}, "order_by": [{"field": "timestamp", "direction": "DESC"}], "pagination": {"limit": 100, "cursor": "eyJpZCI6MTIzNDU2LCJ0aW1lc3RhbXAiOjE3MDAwMDAwMDB9"}}` --- ### `fetch-tgm-token-information` **Nansen Token God Mode — Token Information** — Returns comprehensive token metadata, market metrics (market cap, FDV), and spot trading activity (volume, buys/sells, unique traders, liquidity, holders) for a given token and date range from Nansen's onchain analytics. *Use when:* Use when an agent needs a full token profile including deployment details, social links, market cap, FDV, trading volume, buy/sell counts, unique trader counts, liquidity, and holder data for a specific token over a date range. *Not for:* Do not use for real-time streaming price feeds or order book data; use a dedicated market-data or DEX quote API instead. Not suitable for wallet-level or address-level analytics. **Inputs:** - `token_address` (string, required) — Contract address of the token to query. - `chain` (string, required) — Blockchain network identifier for the token (e.g. 'ethereum', 'base'). - `from_date` (string, required) — Start of the date range for trading metrics (ISO 8601 date string). - `to_date` (string, required) — End of the date range for trading metrics (ISO 8601 date string). **Returns:** Returns a token information object with name, symbol, contract address, logo, deployment date, social links, market cap, FDV, and spot trading metrics (volume, buys, sells, unique traders, liquidity, holders) for the specified date range. **Example:** `{"token_address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913", "chain": "base", "from_date": "2024-01-01", "to_date": "2024-01-31"}` --- ### `fetch-prediction-market-top-holders` **Prediction Market Top Holders** — Returns the top holders for a specified prediction market from Nansen's on-chain analytics data. *Use when:* Use when an agent needs to identify the largest position holders in a prediction market, such as for concentration analysis, whale tracking, or market sentiment research. *Not for:* Do not use for general token holder rankings outside prediction markets; use a standard token holders endpoint instead. Not suitable for real-time streaming data. **Inputs:** - `market` (string, required) — Identifier for the prediction market to query top holders for. **Returns:** Returns a list of top holders for the specified prediction market, including wallet addresses and their respective positions. **Example:** `GET https://api.nansen.ai/api/v1/prediction-market/top-holders?market=0x1234abcd` --- ### `search-nansen-tokens-and-entities` **Nansen Unified Search** — Searches Nansen's blockchain dataset by name, symbol, contract address, or entity name and returns matching tokens and entities with price, volume, market cap, and rank. *Use when:* Use when an agent needs to resolve a token name or symbol to a contract address, identify an unknown contract address, discover known entities (exchanges, funds, public figures), or filter results by chain across Nansen's dataset. *Not for:* Do not use for real-time or streaming price feeds; use token OHLCV endpoints instead. Not suitable for deep on-chain analytics or wallet transaction history. **Inputs:** - `search_query` (string, required) — Token name, symbol, contract address, or entity name to search for. - `result_type` (string) — Filter results by type: "token", "entity", or "any". Defaults to "any". - `chain` (string) — Optional blockchain filter to narrow results (e.g., "ethereum", "solana", "base"). - `limit` (integer) — Maximum number of results to return. Accepts 1–50. Defaults to 25. **Returns:** Returns a tokens array with name, symbol, chain, address, price, volume_24h, market_cap, and rank; an entities array; and a total_results count. **Example:** `{"search_query": "EfPoo4wWgxKVToit7yX5VtXXBrhao4G8L7vrbKy6pump", "result_type": "token", "chain": "solana", "limit": 20}` ---