query-address-info
by binancequery-address-info is a Web3 skill for checking token holdings on a wallet address and supported chain. It returns token name, symbol, price, 24h price change, and quantity held for fast portfolio checks, wallet due diligence, and address monitoring. Use it when you need a structured balance snapshot with less guesswork.
This skill scores 72/100, which means it is listable but best presented with caution: it gives agents a clear wallet-query use case and a concrete API to call, but the repository leaves some workflow details thin enough that users may still need to infer parts of execution. For directory users, that’s enough to justify installation if they want a focused on-chain address lookup skill, not a fully polished end-to-end workflow.
- Explicit trigger intent for wallet balance, token holdings, portfolio, and asset-position questions.
- Concrete GET endpoint with required parameters and request headers, which helps an agent call it directly.
- No placeholder or experimental markers, and the body is substantial enough to show real API usage.
- The repo provides only one skill file and no supporting scripts, references, or rules, so edge-case handling and validation are not well documented.
- The visible example is truncated and the description is very short, which reduces quick-start clarity for first-time users.
Overview of query-address-info skill
What query-address-info does
The query-address-info skill fetches token holdings for a wallet address on a supported chain. It is built for Web3 users who want a quick read on a wallet’s current positions, including token name, symbol, price, 24-hour price change, and quantity held.
Who this skill is for
Use the query-address-info skill for portfolio checks, wallet due diligence, address monitoring, and lightweight on-chain analysis. It is most useful when you already have an address and chain ID and need a structured balance snapshot fast.
When it is the right fit
This skill is a good fit when you need a practical query-address-info guide for answering “what does this wallet hold right now?” It is less useful for transaction history, full DeFi attribution, NFT inventory, or deep analytics beyond active token positions.
Main decision points
The key reason to install query-address-info is speed: it reduces guesswork around the address lookup workflow and shows the required request shape. The main constraint is scope: it focuses on token holdings for a specific address and chain, so you should not expect cross-chain aggregation or historical accounting.
How to Use query-address-info skill
Install and open the skill files
For query-address-info install, add the skill from binance/binance-skills-hub and then read the skill entry file first. Start with SKILL.md, then check any linked repository files if present. In this repo, the skill is self-contained, so SKILL.md is the primary source of truth.
What input the skill needs
To use query-address-info well, provide:
- a wallet address, such as a
0x...EVM address - a supported
chainId, such as56for BSC or8453for Base - an
offsetvalue for pagination, usually0for the first page
A weak prompt like “check this wallet” leaves too much ambiguity. A stronger prompt like “Use query-address-info for address 0x... on chain 56, return the active token positions and note any large balance concentrations” gives the skill enough context to return a focused result.
Practical workflow for better results
Use query-address-info usage in three steps:
- Confirm the chain and address are correct.
- Ask for the first page of holdings with
offset=0. - If the wallet is large, continue with later offsets to inspect more positions.
For analysis tasks, ask the model to summarize holdings by token concentration, stablecoin exposure, or notable price moves. That turns a raw balance list into a useful wallet-readout instead of a plain API dump.
Files and details to read first
If you are adapting the skill, read the request parameters, headers, and example request in SKILL.md before building prompts or automations. Those details matter because the endpoint expects a specific address, chain ID, and pagination format, and incorrect values are the most common cause of empty or misleading results.
query-address-info skill FAQ
Is query-address-info only for Web3 addresses?
Yes. The query-address-info for Web3 use case is the core design. It is meant for on-chain wallet addresses and token positions, not email accounts, exchange profiles, or off-chain identity data.
How is this different from a normal prompt?
A normal prompt can describe the goal, but the query-address-info skill gives you the exact API-oriented workflow and required inputs. That usually means fewer formatting mistakes, less back-and-forth, and more reliable outputs when you need wallet holdings quickly.
Is it beginner-friendly?
Yes, if you already know the wallet address and chain. The main beginner challenge is choosing the correct chain ID and understanding that this skill returns active positions, not every kind of asset data a wallet might have.
When should I not use it?
Do not use query-address-info if you need historical PnL, full transaction tracing, cross-chain portfolio aggregation, or NFT analysis. Those jobs need different tools and data sources.
How to Improve query-address-info skill
Give the cleanest possible address and chain
The best way to improve query-address-info results is to supply a valid checksum-style address and the exact chain ID. If either value is wrong, the output may be incomplete or point to the wrong wallet context.
Ask for the analysis you actually need
Instead of asking only for balances, specify the decision you want to make. For example: “Summarize the top 5 holdings by value,” “Flag stablecoin-heavy wallets,” or “Highlight tokens with sharp 24h moves.” That helps the skill turn a position list into a more useful query-address-info guide output.
Use pagination intentionally
Large wallets may have more positions than fit on one page. If the first response looks incomplete, continue with the next offset rather than assuming the wallet is empty. This matters most for active traders, LPs, and multi-asset wallets.
Verify edge cases before acting
Watch for wrapped assets, illiquid tokens, and stale-looking balances. If you are using the result for screening or reporting, compare the top holdings against the wallet’s likely strategy and re-run with a fresh prompt if the output does not match the expected chain or address.