Query Token Info
Look up Binance-listed token prices, liquidity, and risk tags from the terminal before you wire DeFi or trading features into your product.
Overview
query-token-info is an agent skill most often used in Validate (also Idea research) that queries Binance token search and metadata through a documented Node CLI.
Install
npx skills add https://github.com/binance/binance-skills-hub --skill query-token-infoWhat is this skill?
- CLI `search` by keyword, symbol, or contract with optional chainId filters (e.g. BSC `56`, multi-chain lists)
- Returns USD price, 24h change, volume, market cap, liquidity, and categorized tagsInfo for risk/community signals
- `meta` and related commands for static token metadata via `scripts/cli.mjs` with JSON params
- Documented exit codes: 0 success, 1 usage/upstream error, 3 network failure
- Stable `tokenId` across contract address changes for dependable catalog keys in your own tooling
- Documented CLI exit codes: 0, 1, and 3
- Search supports comma-separated multi-chain `chainIds`
Adoption & trust: 5.2k installs on skills.sh; 881 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need trustworthy token price, liquidity, and risk-tag data while scoping a crypto feature, but you do not want to maintain bespoke Binance API glue in every repo.
Who is it for?
Indie builders validating DeFi, trading bots, or portfolio tools who already use Node and want copy-paste CLI commands in agent workflows.
Skip if: Teams that need full order execution, custody, or compliance-grade market data without reviewing upstream Binance terms and their own regulatory obligations.
When should I use this skill?
User needs Binance token search, metadata, or market fields via the hub CLI during research or integration work.
What do I get? / Deliverables
Your agent returns structured token rows (price, volume, tags, contract addresses) from one CLI invocation so you can proceed to integration design or reject weak markets early.
- CLI JSON output with token price, volume, tags, and identifiers
- Documented command invocation for agent replay
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Validate because solo builders most often install this while scoping token economics, comparables, and market sanity checks before committing to a crypto-facing build. Pricing subphase fits token search, 24h volume, market cap, and tag-based risk signals used to judge whether an asset or chain is worth integrating.
Where it fits
Scan listed symbols and liquidity on BSC before picking which chain your MVP will support first.
Compare 24h volume and market cap across two competitor token tickers you might list in your app.
Fetch stable `tokenId` and contract address fields to seed your backend config or agent tool schema.
How it compares
Use as a Binance-focused CLI skill package, not a generic MCP market-data server or an on-chain indexer.
Common Questions / FAQ
Who is query-token-info for?
Solo and indie developers building crypto-adjacent SaaS, CLIs, or agents who want Binance token lookup commands the agent can run with JSON parameters.
When should I use query-token-info?
During Validate pricing research when comparing tokens and chains, during Idea competitor/discovery research for listed assets, and during Build integrations when you need canonical `tokenId` and contract fields before coding.
Is query-token-info safe to install?
It runs local Node scripts and calls network APIs; review the Security Audits panel on this page, verify the skill source, and never paste secrets into CLI JSON params.
SKILL.md
READMESKILL.md - Query Token Info
# query-token-info — CLI Reference Complete reference for every command in `scripts/cli.mjs`. **Invocation pattern:** `node <skill-dir>/scripts/cli.mjs <command> '<json_params>'` **Exit codes:** `0` success · `1` usage/upstream error · `3` network failure --- ## `search` — Search tokens by keyword ```bash node <skill-dir>/scripts/cli.mjs search '{"keyword":"<keyword>","chainIds":"56"}' ``` ### Parameters | Param | Type | Required | Description | |---|---|---|---| | `keyword` | string | **yes** | Name / symbol / contract address | | `chainIds` | string | no | Comma-separated chainIds (e.g. `"56"`, `"1,56,8453,CT_501"`); default: all | | `orderBy` | string | no | Sort key, e.g. `volume24h` | ### Return fields (under `.data[]`) | Field | Type | Description | |---|---|---| | `chainId` | string | Chain identifier (e.g. `"56"` = BSC) | | `contractAddress` | string | Token contract address | | `tokenId` | string | Binance-internal token ID (stable across address changes) | | `name`, `symbol` | string | Token display names | | `icon` | string | Logo path — prefix with `https://bin.bnbstatic.com` | | `price`, `percentChange24h` | string | Latest USD price and 24h change (%) | | `volume24h`, `marketCap`, `liquidity` | string | All USD; string-encoded decimals | | `tagsInfo` | object | Risk / recognition tags, categorized (e.g. `"Sensitive Events": [...]`, `"Community Recognition Level": [...]`) | --- ## `meta` — Static token metadata ```bash node <skill-dir>/scripts/cli.mjs meta '{"chainId":"56","contractAddress":"0x..."}' ``` ### Parameters | Param | Type | Required | Description | |---|---|---|---| | `chainId` | string | **yes** | Chain identifier | | `contractAddress` | string | **yes** | Token contract address (case-insensitive) | ### Return fields (under `.data`) | Field | Type | Description | |---|---|---| | `tokenId` | string | Binance-internal stable ID | | `name`, `symbol`, `decimals` | — | Display name, ticker, precision | | `chainName`, `chainIconUrl` | string | Chain display info | | `links` | array of `{label, link}` | Website / whitepaper / social links | | `aiNarrativeFlag` | number | `1` = AI has narrative summary available | | `nativeAddressFlag` | boolean | `true` = native chain coin (not an ERC-20) | `links[]` entries are `{label, link}` — labels include `"website"`, `"whitepaper"`, social platforms. --- ## `dynamic` — Real-time market data ```bash node <skill-dir>/scripts/cli.mjs dynamic '{"chainId":"56","contractAddress":"0x..."}' ``` ### Parameters | Param | Type | Required | Description | |---|---|---|---| | `chainId` | string | **yes** | Chain identifier | | `contractAddress` | string | **yes** | Token contract address | ### Return fields (under `.data`) Price + volume/buy/sell breakdowns across multiple windows (5m, 1h, 4h, 24h), separated by on-chain vs Binance-routed: | Field pattern | Meaning | |---|---| | `price`, `nativeTokenPrice` | Current USD price and chain-native price | | `volume{5m,1h,4h,24h}` | Total trading volume in window (USD) | | `volume{window}{Buy,Sell}` | Direction breakdown | | `volume{window}Binance` | Binance-routed subset | | `volume{window}Net{Buy,Binance}` | Net flow = Buy − Sell | | `holders` | Holder count (if available) | | `liquidity` | Current liquidity in USD | --- ## `kline` — Candlestick OHLCV ```bash node <skill-dir>/scripts/cli.mjs kline '{"chainId":"56","contractAddress":"0x...","interval":"1h","limit":24}' ``` ### Parameters | Param | Type | Required | Description | |---|---|---|---| | `chainId` | string | **yes** | Chain identifier — `1` (Ethereum) / `56` (BSC) / `8453` (Base) / `CT_501` (Solana) | | `contractAddress` | string | **yes** | Token contract address | | `interval` | string | **yes** | Candle size: `1s` / `1min` / `3min` / `5min` / `15min` / `30min` / `1h` / `2h` / `4h` / `6h` / `8h` / `12h` / `1d` / `3d` / `1w` / `1m` | | `limit` | number | no | Optional. Max 500 per request. Has higher priority than `from` when both provided. | |