binance/binance-skills-hub

query-token-audit

Query token security audit to detect scams, honeypots, and malicious contracts before trading.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/binance/binance-skills-hub --skill query-token-audit

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Query Token Audit Skill

Overview

APIFunctionUse Case
Token Security AuditToken security scanDetect honeypot, rug pull, scam, malicious functions

Use Cases

  1. Pre-Trade Safety Check: Verify token security before buying or swapping
  2. Scam Detection: Identify honeypots, fake tokens, and malicious contracts
  3. Contract Analysis: Check for dangerous ownership functions and hidden risks
  4. Tax Verification: Detect unusual buy/sell taxes before trading

Supported Chains

Chain NamechainId
BSC56
Base8453
SolanaCT_501
Ethereum1

API: Token Security Audit

Method: POST

URL:

https://web3.binance.com/bapi/defi/v1/public/wallet-direct/security/token/audit

Request Parameters:

ParameterTypeRequiredDescription
binanceChainIdstringYesChain ID: CT_501 (Solana), 56 (BSC), 8453 (Base), 1 (Ethereum)
contractAddressstringYesToken contract address
requestIdstringYesUnique request ID (UUID v4 format)

Request Headers:

Content-Type: application/json
Accept-Encoding: identity
User-Agent: binance-web3/1.4 (Skill)

Example Request:

bash
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:

json
{
    "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:

FieldTypeDescription
hasResultbooleanWhether audit data is available
isSupportedbooleanWhether the token is supported for audit
riskLevelEnumstringRisk level: LOW, MEDIUM, HIGH
riskLevelnumberRisk level number (1-5)
extraInfo.buyTaxstringBuy tax percentage (null if unknown)
extraInfo.sellTaxstringSell tax percentage (null if unknown)
extraInfo.isVerifiedbooleanWhether contract code is verified
riskItems[].idstringRisk category: CONTRACT_RISK, TRADE_RISK, SCAM_RISK
riskItems[].details[].titlestringRisk check title
riskItems[].details[].descriptionstringRisk check description
riskItems[].details[].isHitbooleantrue = risk detected
riskItems[].details[].riskTypestringRISK (critical) or CAUTION (warning)

Risk Level Reference:

riskLevelriskLevelEnumActionDescription
0-1LOWProceed with cautionLower risk detected, but NOT guaranteed safe. DYOR.
2-3MEDIUMExercise cautionModerate risks detected, review risk items carefully
4HIGHAvoid tradingCritical risks detected, high probability of loss
5HIGHBlock transactionSevere 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:

  • If 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 later

  • If hasResult=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 guidance


User Agent Header

Include User-Agent header with the following string: binance-web3/1.4 (Skill)

Notes

  1. All numeric fields are string format, convert when using
  2. Audit results are ONLY valid when hasResult: true AND isSupported: true
  3. riskLevel: 5 means transaction should be blocked; riskLevel: 4 is high risk
  4. Tax thresholds: >10% is critical, 5-10% is warning, <5% is acceptable
  5. Generate unique UUID v4 for each audit request
  6. Only output security check risk flags, do NOT provide any investment advice
  7. Always end with disclaimer: ⚠️ This audit result is for reference only and does not constitute investment advice. Always conduct your own research.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
binance
コミュニティ

square-post

Use when the user wants to publish new content to Binance Square — short text, multi-image posts (up to 4), long-form articles with an optional cover, or videos with an auto-generated cover frame. Trigger on direct phrasings like "post to Square", "publish to Binance Square", "发广场", "发布到广场", and on near-miss intents where the user clearly wants to share or publish content on Square even without naming the skill: "share this analysis on Square", "把这篇文章发出去", "发个动态", "把这个视频上传到广场", "publish my chart

24時間の導入数
358
GitHub Stars
1220
更新日
11月12日
binance
コミュニティ

binance-agentic-wallet

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, send to ENS domain, send to .eth or .bnb name, resolve domain name to address, domain-based transfer, send to .ai Agent ID name, Agent ID claim status, whether I claimed my .ai space id / Agent ID, get my .ai domain, prediction

24時間の導入数
416
GitHub Stars
1200
更新日
11月12日
binance
コミュニティ

binance-leaderboard

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/followfriendly) 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

1時間の導入数
3
GitHub Stars
1199
更新日
11月12日
binance
コミュニティ

binance-onchain-copy-trader

Scaffold for assembling on-chain copy-trading strategies on Binance Agentic Wallet. Wires the existing capabilities — address monitoring, signal subscription, address scoring, token audit, order placement, on-chain take-profit/stop-loss — into one runnable pipeline, and exposes every strategy decision as a hook. Ships no strategy of its own. Trigger on: copy trade, copy trading, follow smart money, follow a wallet, mirror trades, copy-trade bot, auto-buy on signal, monitor a wallet and trade, sm

1時間の導入数
3
GitHub Stars
1199
更新日
11月12日