query-token-audit
Conduct security audits for tokens, detecting potential honeypots, rug pulls, scams, and malicious features to ensure transaction security.
npx skills add binance/binance-skills-hub --skill query-token-auditBefore / After Comparison
1 组Before conducting a token security audit, I might blindly invest in or trade emerging cryptocurrency tokens. This exposes me to significant risks, such as encountering 'honeypots,' 'rug pulls,' or purchasing tokens with malicious functionalities, leading to asset loss.
With the Query Token Audit skill, I can perform a comprehensive security scan of token contracts before trading. This skill can detect potential malicious functionalities, ownership risks, and known scam patterns, providing crucial security information for my investment decisions and significantly reducing risks.
description SKILL.md
query-token-audit
Query Token Audit Skill
Overview
API Function Use Case
Token Security Audit Token security scan Detect honeypot, rug pull, scam, malicious functions
Use Cases
-
Pre-Trade Safety Check: Verify token security before buying or swapping
-
Scam Detection: Identify honeypots, fake tokens, and malicious contracts
-
Contract Analysis: Check for dangerous ownership functions and hidden risks
-
Tax Verification: Detect unusual buy/sell taxes before trading
Supported Chains
Chain Name chainId
BSC 56
Base 8453
Solana CT_501
Ethereum 1
API: Token Security Audit
Method: POST
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.
Result Validity:
Audit results are ONLY valid when both conditions are met:
-
hasResult: true— Audit data is available -
isSupported: true— Token is supported for audit
When invalid, do NOT display risk level or security checks.
User Agent Header
Include User-Agent header with the following string: binance-web3/1.4 (Skill)
Notes
-
All numeric fields are string format, convert when using
-
Audit results are ONLY valid when
hasResult: trueANDisSupported: true -
riskLevel: 5means transaction should be blocked;riskLevel: 4is high risk -
Tax thresholds: >10% is critical, 5-10% is warning, <5% is acceptable
-
Generate unique UUID v4 for each audit request
-
Only output security check risk flags, do NOT provide any investment advice
-
Always end with disclaimer:
⚠️ This audit result is for reference only and does not constitute investment advice. Always conduct your own research.
Weekly Installs1.2KRepositorybinance/binance…ills-hubGitHub Stars473First SeenMar 2, 2026Security AuditsGen Agent Trust HubPassSocketPassSnykPassInstalled oncodex1.2Kopencode1.2Kgemini-cli1.2Kamp1.2Kgithub-copilot1.2Kcursor1.2K
forumUser Reviews (0)
Write a Review
No reviews yet
Statistics
User Rating
Rate this Skill