skills/binance-web3/query-token-audit/SKILL.md
Query token security audit to detect scams, honeypots, and malicious contracts before trading. Returns comprehensive security analysis including contract risks, trading risks, and scam detection. Use when users ask "is this token safe?", "check token security", "audit token", or before any swap.
npx skillsauth add binance/binance-skills-hub query-token-auditInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| API | Function | Use Case | |-----|---------------------|----------| | Token Security Audit | Token security scan | Detect honeypot, rug pull, scam, malicious functions |
| Chain Name | chainId | |------------|---------| | BSC | 56 | | Base | 8453 | | Solana | CT_501 | | Ethereum | 1 |
URL:
https://web3.binance.com/bapi/defi/v1/public/wallet-direct/security/token/audit
Request Parameters:
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| binanceChainId | string | Yes | Chain ID: CT_501 (Solana), 56 (BSC), 8453 (Base), 1 (Ethereum) |
| contractAddress | string | Yes | Token contract address |
| requestId | string | Yes | Unique request ID (UUID v4 format) |
Request Headers:
Content-Type: application/json
Accept-Encoding: identity
User-Agent: binance-web3/1.4 (Skill)
Example Request:
curl --location 'https://web3.binance.com/bapi/defi/v1/public/wallet-direct/security/token/audit' \
--header 'Content-Type: application/json' \
--header 'source: agent' \
--header 'Accept-Encoding: identity' \
--header 'User-Agent: binance-web3/1.4 (Skill)' \
--data '{
"binanceChainId": "56",
"contractAddress": "0x55d398326f99059ff775485246999027b3197955",
"requestId": "'$(uuidgen)'"
}'
Response Example:
{
"code": "000000",
"data": {
"requestId": "d6727c70-de6c-4fad-b1d7-c05422d5f26b",
"hasResult": true,
"isSupported": true,
"riskLevelEnum": "LOW",
"riskLevel": 1,
"extraInfo": {
"buyTax": "0",
"sellTax": "0",
"isVerified": true
},
"riskItems": [
{
"id": "CONTRACT_RISK",
"name": "Contract Risk",
"details": [
{
"title": "Honeypot Risk Not Found",
"description": "A honeypot is a token that can be bought but not sold",
"isHit": false,
"riskType": "RISK"
}
]
}
]
},
"success": true
}
Response Fields:
| Field | Type | Description |
|-----------------------------------|------|-----------------------------------------------------------|
| hasResult | boolean | Whether audit data is available |
| isSupported | boolean | Whether the token is supported for audit |
| riskLevelEnum | string | Risk level: LOW, MEDIUM, HIGH |
| riskLevel | number | Risk level number (1-5) |
| extraInfo.buyTax | string | Buy tax percentage (null if unknown) |
| extraInfo.sellTax | string | Sell tax percentage (null if unknown) |
| extraInfo.isVerified | boolean | Whether contract code is verified |
| riskItems[].id | string | Risk category: CONTRACT_RISK, TRADE_RISK, SCAM_RISK |
| riskItems[].details[].title | string | Risk check title |
| riskItems[].details[].description | string | Risk check description |
| riskItems[].details[].isHit | boolean | true = risk detected |
| riskItems[].details[].riskType | string | RISK (critical) or CAUTION (warning) |
Risk Level Reference:
| riskLevel | riskLevelEnum | Action | Description | |-----------|---------------|--------|-------------| | 0-1 | LOW | Proceed with caution | Lower risk detected, but NOT guaranteed safe. DYOR. | | 2-3 | MEDIUM | Exercise caution | Moderate risks detected, review risk items carefully | | 4 | HIGH | Avoid trading | Critical risks detected, high probability of loss | | 5 | HIGH | Block transaction | Severe risks confirmed, do NOT proceed |
IMPORTANT: LOW risk does NOT mean "safe." Audit results are point-in-time snapshots. Project teams can modify contracts or restrict liquidity after purchase. These risks cannot be predicted in advance.
Response Handling:
hasResult=false OR isSupported=false:
→ Reply: "Security audit data is not available for this token on this chain."
→ Do NOT show riskLevel, riskLevelEnum, or riskItems (data is unreliable when either field is false)
→ You may suggest the user verify the contract address and chain, or try again laterhasResult=true AND isSupported=true:
→ Show the full audit result including risk level, tax info, and all risk items
→ Apply the Risk Level Reference table above for actionable guidanceInclude User-Agent header with the following string: binance-web3/1.4 (Skill)
hasResult: true AND isSupported: trueriskLevel: 5 means transaction should be blocked; riskLevel: 4 is high risk⚠️ This audit result is for reference only and does not constitute investment advice. Always conduct your own research.development
Use when the user mentions wallet connect/sign in/sign out, check balance, send/transfer tokens, swap/buy/sell tokens, DEX trade, limit/market order, cancel order, get a quote, transaction history, wallet settings, daily limit, slippage, MEV protection, supported chains, prediction market, place prediction, redeem winnings, prediction PnL, x402 payment, HTTP 402 Payment Required, check/revoke/manage token approvals, DeFi protocols, staking, liquidity pool, LP, yield farming, deposit, redeem, stake, unstake, claim rewards/fees, health factor, APY, TVL, sign external transaction, contract call, sign message, EIP-712, developer mode, speed up/cancel/replace transaction, pending/stuck transactions, or any on-chain wallet operation.
tools
Use binance-cli for Binance Spot, Futures (USD-S), and Convert. Requires auth.
development
Wallet tracking and monitoring on Binance Web3. Monitor token/trade activity for private groups or public Smart Money/KOL data. Four domains: (A) Discovery — consensus, pioneer, leaderboard diff, token buyer lookup, time-window summaries, similar wallets; (B) Evaluation — token risk (tokenRiskLevel ≥ 3), group rhythm, follow list assessment, token heat; (C) Replay — 4h summary, Accumulation/Distribution, sector rotation, anomaly orders, round-trip, first-mover/leader-follower, wake-up, bot-like; (D) Management — group create/rename, batch import, label update, link, follow list; (E) Real-time — WebSocket push for Smart Money, KOL, wallet-level, and address-level trade events. Trigger on: wallet tracker, monitoring, consensus, pioneer, accumulation, Distribution, Sector Rotation, Anomaly Large Order, round-trip, first-mover, wake-up, bot-like, token risk, token heat, group profile, similar wallets, group management, address import, follow list, real-time push, WebSocket — even without "tracker" explicitly.
development
On-chain wallet leaderboard and Gem Hunter analysis on Binance Web3. Query top trader rankings by PnL, win rate, volume, trade count, or token count across BSC/Solana/Base/ETH. Analyze individual wallet addresses with a 6-dimension scoring model (winrate/stability/drawdown/ tags/pnl/follow_friendly) plus AI archetype overlay. Query Gem Hunter to find wallets holding specific tokens. Save and load preset filter conditions and Gem Hunter configs. Trigger whenever the user mentions leaderboard, top traders, wallet analysis, Address Analysis, AddressScore, Gem Hunter, or wants to evaluate a wallet's trading quality — even if they don't say "leaderboard" explicitly.