query-token-info

Query token metadata, real-time market data, and K-Line candlesticks via Binance Web3 APIs.

1|Updated May 10, 2026
One-click install
npx skills add https://github.com/Tgoldi/claude-skills --skill query-token-info-tgoldi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: query-token-info
Source: https://github.com/Tgoldi/claude-skills/tree/main/query-token-info
Command: npx skills add https://github.com/Tgoldi/claude-skills --skill query-token-info-tgoldi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finding reliable token information across chains requires juggling multiple block explorers and data sources. This Skill consolidates token search, metadata, real-time market data, and candlestick charts into a single set of Binance Web3 API endpoints. ## Core Features & Use Cases - Token Search: Find tokens by name, symbol, or contract address across BSC, Base, and Solana, with sorting by volume. - Metadata & Social Links: Retrieve token name, symbol, logo, decimals, creator address, audit flags, and official social links for project research. - Real-Time Market Data: Get price, price changes across multiple timeframes, volume, liquidity, market cap, holder counts, and smart money/KOL holding percentages. - K-Line Candlesticks: Fetch OHLCV candlestick data across 16 intervals (1s to 1 month) for technical analysis. - Use Case: A user asks "What's the current price and holder distribution of this token on BSC?" — the Skill calls the dynamic data endpoint and returns price, liquidity, top-10 holder percentage, and KOL holdings in one response. ## Quick Start Ask the assistant to look up a token's price, market data, or candlestick chart by providing its name, symbol, or contract address and chain.

Frequently Asked Questions about query-token-info

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search for a token by contract address?

Call the token search endpoint with the contract address as the keyword parameter, optionally filtering by chainIds such as 56 for BSC or 8453 for Base. The response returns matching tokens with price, volume, market cap, and social links.

How do I get real-time price and holder data for a token?

Use the token dynamic data endpoint with the chainId and contractAddress parameters. It returns current price, percent changes across 5m to 24h, volume, liquidity, market cap, holder count, and top-10 holder percentage.

Which chains does the Binance Web3 token API support?

Token search, metadata, and dynamic data support BSC (chainId 56), Base (chainId 8453), and Solana (chainId CT_501). The K-Line endpoint additionally supports Ethereum via the platform parameter value eth.

How do I fetch candlestick chart data for a token?

Call the K-Line endpoint with the token address, platform (eth, bsc, solana, or base), and an interval such as 1min, 1h, or 1d. Each candle is returned as an array of open, high, low, close, volume, timestamp, and transaction count.

Why are numeric fields returned as strings in the API response?

All numeric fields like price, volume, and market cap are string-encoded to preserve precision for large decimal values. Convert them to numbers in your code before performing calculations or comparisons.

What is the difference between chainId and platform parameters?

The search, metadata, and dynamic data endpoints use numeric chainId values like 56 or CT_501, while the K-Line endpoint uses string platform values like bsc or solana. Check the mapping table before constructing K-Line requests.