Index of every page on this site: llms.txt
All skills
binance avatar

/binance-agentic-wallet

@f422171 #1 trending · Oct 2026
by binancebinance/binance-skills-hub1.1k stars
249
Run it yourself

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, 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, gas price, gas fee, network fee, fee levels, gas tiers, or any on-chain wallet operation.

Use this Skill: https://skilld.dev/gh/binance/binance-skills-hub/binance-agentic-wallet

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesapprovals.md

≈1.8k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Token Approvals

Manage token approvals: view, filter, and revoke EVM token authorizations.

approvals list

List all active token approvals, optionally filtered by chain or spender.

Syntax

baw approvals list [--binanceChainId <binanceChainId>] [--spender <spender>] --json

Parameters

Parameter Required Default Description
--binanceChainId No — Chain ID filter (e.g. 56 for BSC). For other EVM chains, see wallet chains
--spender No — Filter by spender contract address

Example

# List all approvals
baw approvals list --json

# List approvals on BSC only
baw approvals list --binanceChainId 56 --json

# List approvals for a specific spender
baw approvals list --spender <spender_address> --json

Response

{
  "success": true,
  "data": {
    "list": [
      {
        "tokenSymbol": "USDT",
        "tokenContract": "<token_contract_address>",
        "tokenDecimals": 18,
        "spender": "<spender_address>",
        "spenderName": "PancakeSwap",
        "spenderIcon": "https://example.com/pancakeswap.png",
        "amount": "unlimited",
        "riskyLevel": "low",
        "riskyMsg": null,
        "binanceChainId": "56",
        "chainName": "BSC",
        "type": "approve",
        "noInteractive": null,
        "approveTime": 1717401600000
      },
      {
        "tokenSymbol": "USDC",
        "tokenContract": "<token_contract_address_2>",
        "tokenDecimals": 18,
        "spender": "<spender_address_2>",
        "spenderName": "Uniswap Permit2",
        "spenderIcon": "https://example.com/uniswap.png",
        "amount": "1000.0",
        "riskyLevel": "high",
        "riskyMsg": "Spender contract is unverified",
        "binanceChainId": "56",
        "chainName": "BSC",
        "type": "permit2",
        "noInteractive": true,
        "approveTime": 1715587200000
      }
    ],
    "offset": 0,
    "limit": 20,
    "total": 2
  }
}

approvals detail

Get detailed information about a specific token approval, including approval history.

Syntax

baw approvals detail --binanceChainId <binanceChainId> --tokenContract <tokenContract> --spender <spender> --type <type> --json

Parameters

Parameter Required Default Description
--binanceChainId Yes — Chain ID (e.g. 56 for BSC). For other EVM chains, see wallet chains
--tokenContract Yes — Token contract address
--spender Yes — Spender contract address
--type Yes — Approval type: approve or permit2

Example

baw approvals detail --binanceChainId 56 --tokenContract <token_contract_address> --spender <spender_address> --type approve --json

Response

{
  "success": true,
  "data": {
    "detail": {
      "tokenSymbol": "USDT",
      "tokenContract": "<token_contract_address>",
      "tokenDecimals": 18,
      "balance": "1500.75",
      "price": "1.00",
      "spender": "<spender_address>",
      "spenderName": "PancakeSwap",
      "spenderIcon": "https://example.com/pancakeswap.png",
      "amount": "unlimited",
      "riskyLevel": "low",
      "riskyMsg": null,
      "binanceChainId": "56",
      "type": "approve",
      "permit2ContractAddress": null,
      "expireTime": null,
      "approveTime": 1717401600000
    },
    "records": [
      {
        "txHash": "<tx_hash>",
        "action": "approve",
        "amount": "unlimited",
        "timestamp": 1717401600000,
        "status": "confirmed"
      },
      {
        "txHash": "<tx_hash_2>",
        "action": "approve",
        "amount": "500.0",
        "timestamp": 1715587200000,
        "status": "confirmed"
      }
    ]
  }
}

Approval History

The records array contains the most recent approval operation history (up to 20 records) for this token-spender pair. Each record includes:

  • txHash — the transaction hash
  • action — operation type: approve, revoke, permit2_approve, etc.
  • amount — approved amount at that time
  • timestamp — operation time (unix ms)
  • status — confirmed or failed

approvals revoke

Revoke a token approval to remove a spender's permission.

Syntax

baw approvals revoke --binanceChainId <binanceChainId> --tokenContract <tokenContract> --spender <spender> --type <type> --json

Parameters

Parameter Required Default Description
--binanceChainId Yes — Chain ID (e.g. 56 for BSC). For other EVM chains, see wallet chains
--tokenContract Yes — Token contract address
--spender Yes — Spender contract address
--type Yes — Approval type: approve or permit2

Revoke always runs at the MEDIUM gas level; there is no gas parameter to set.

Example

baw approvals revoke --binanceChainId 56 --tokenContract <token_contract_address> --spender <spender_address> --type approve --json

Response

{
  "success": true,
  "data": {
    "orderId": "9876543210",
    "status": "BROADCASTED",
    "txHash": "<tx_hash>"
  }
}

Important: a txHash does not mean on-chain confirmation

A successful response with a txHash means the revoke transaction has been broadcast to the network — it does not mean it has been confirmed or finalized on-chain. The approval remains effective until the transaction is confirmed.

After receiving a txHash, always tell the user:

  1. The revoke transaction has been submitted and is pending confirmation.
  2. They can track its status with wallet tx-history.
  3. The approval is still active until on-chain confirmation — they should wait before considering the revocation complete.

Nullable Fields

The following fields may return null — handle gracefully when displaying:

Field Appears In When Null
spenderIcon list / detail Do not display an icon
spenderName list / detail Display the full spender address instead
riskyMsg list / detail Do not display risk description
permit2ContractAddress detail Normal when type is approve
noInteractive list Do not display "no interaction" label
expireTime detail Display as "never expires"

Source: SKILL.md on GitHub

Skill behaviors

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

Third-party checks

2 warnings1d3 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    This skill provides a secure and well-structured interface for the Binance Agentic Wallet CLI. It includes numerous security guardrails such as mandatory user confirmations for all financial transactions, automatic token security audits before trading, and explicit defenses against prompt injection from on-chain data or third-party API outputs. All external dependencies and network calls are directed to official Binance or affiliate infrastructure.

  • Socket3d

    1 alert: gptSecurity

  • Snyk3d

    Risk: MEDIUM · 1 issue

Provenance

Signed by skilld at f422171. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 13 hours ago.

Activeupdated 4 days ago

Capability

Other metadata
metadata
{
  "author": "binance-web3-team",
  "version": "1.13.0",
  "requiredCliVersion": "1.11.0",
  "openclaw": {
    "requires": {
      "bins": [
        "baw"
      ]
    },
    "install": [
      {
        "kind": "node",
        "package": "@binance/agentic-wallet",
        "bins": [
          "baw"
        ],
        "label": "Install Binance Agentic Wallet CLI (npm)"
      }
    ]
  }
}

README badge

README badge for binance/binance-skills-hub/binance-agentic-wallet