⚡

// Skill profile

Binance Assets Skill

Name: Binance Assets Skill
Author: binance-skills-hub

name: assets

by binance-skills-hub · published 2026-04-01

邮件处理日历管理

Total installs

Stars

★ 0

Last updated

2026-04

// Install command

$ claw add gh:binance-skills-hub/binance-skills-hub-binance-assets

View on GitHub

// Full documentation

---

name: assets

description: Binance Assets request using the Binance API. Authentication requires API key and secret key.

metadata:

version: 1.0.0

author: Binance

license: MIT

---

# Binance Assets Skill

Assets request on Binance using authenticated API endpoints. Requires API key and secret key for certain endpoints. Return the result in JSON format.

Quick Reference

|----------|-------------|----------|----------|----------------|

| `/sapi/v1/localentity/broker/deposit/provide-info` (PUT) | Submit Deposit Questionnaire (For local entities that require travel rule) (supporting network) (USER_DATA) | subAccountId, depositId, questionnaire, beneficiaryPii, signature | network, coin, amount, address, addressTag | Yes |

| `/sapi/v1/localentity/broker/withdraw/apply` (POST) | Broker Withdraw (for brokers of local entities that require travel rule) (USER_DATA) | address, coin, amount, withdrawOrderId, questionnaire, originatorPii, signature | addressTag, network, addressName, transactionFeeFlag, walletType | Yes |

| `/sapi/v2/localentity/deposit/history` (GET) | Deposit History V2 (for local entities that required travel rule) (supporting network) (USER_DATA) | None | depositId, txId, network, coin, retrieveQuestionnaire, startTime, endTime, offset, limit | Yes |

| `/sapi/v1/localentity/deposit/history` (GET) | Deposit History (for local entities that required travel rule) (supporting network) (USER_DATA) | None | trId, txId, tranId, network, coin, travelRuleStatus, pendingQuestionnaire, startTime, endTime, offset, limit | Yes |

| `/sapi/v2/localentity/withdraw/history` (GET) | Withdraw History V2 (for local entities that require travel rule) (supporting network) (USER_DATA) | None | trId, txId, withdrawOrderId, network, coin, travelRuleStatus, offset, limit, startTime, endTime, recvWindow | Yes |

| `/sapi/v1/localentity/withdraw/history` (GET) | Withdraw History (for local entities that require travel rule) (supporting network) (USER_DATA) | None | trId, txId, withdrawOrderId, network, coin, travelRuleStatus, offset, limit, startTime, endTime, recvWindow | Yes |

| `/sapi/v1/localentity/withdraw/apply` (POST) | Withdraw (for local entities that require travel rule) (USER_DATA) | coin, address, amount, questionnaire | withdrawOrderId, network, addressTag, transactionFeeFlag, name, walletType, recvWindow | Yes |

---

Parameters

Common Parameters

* **recvWindow**: (e.g., 5000)

* **type**:

* **startTime**: (e.g., 1623319461670)

* **endTime**: (e.g., 1641782889000)

* **limit**: min 7, max 30, default 7 (e.g., 7)

* **spotBNBBurn**: "true" or "false"; Determines whether to use BNB to pay for trading fees on SPOT

* **interestBNBBurn**: "true" or "false"; Determines whether to use BNB to pay for margin loan's interest

* **asset**: If asset is blank, then query all positive assets user have.

* **accountType**: `SPOT` or `MARGIN`,default `SPOT` (e.g., SPOT)

* **tranId**: The transaction id (e.g., 1)

* **clientTranId**: The unique flag (e.g., 1)

* **startTime**: (e.g., 1623319461670)

* **endTime**: (e.g., 1641782889000)

* **current**: current page, default 1, the min value is 1 (e.g., 1)

* **size**: page size, default 10, the max value is 100 (e.g., 10)

* **asset**:

* **clientId**: A unique id for the request (e.g., 1)

* **targetAsset**:

* **thirdPartyClientId**: (e.g., 1)

* **dustQuotaAssetToTargetAssetPrice**: (e.g., 1.0)

* **targetAsset**:

* **needBtcValuation**: true or false

* **email**:

* **type**: Delegate/Undelegate

* **fromSymbol**:

* **toSymbol**:

* **quoteAsset**: `USDT`, `ETH`, `USDC`, `BNB`, etc. default `BTC` (e.g., BTC)

* **symbol**:

* **needBtcValuation**: Whether need btc valuation or not.

* **amount**: (e.g., 1.0)

* **coin**:

* **network**:

* **amount**: (e.g., 1.0)

* **includeSource**: Default: `false`, return `sourceAddress`field when set to `true`

* **coin**:

* **status**: 0(0:Email Sent, 2:Awaiting Approval 3:Rejected 4:Processing 6:Completed)

* **offset**: Default: 0

* **txId**: (e.g., 1)

* **depositId**: Deposit record Id, priority use (e.g., 1)

* **subAccountId**: Sub-accountId of Cloud user (e.g., 1)

* **subUserId**: Sub-userId of parent user (e.g., 1)

* **withdrawOrderId**: client side id for withdrawal, if provided in POST `/sapi/v1/capital/withdraw/apply`, can be used here for query. (e.g., 1)

* **idList**: id list returned in the response of POST `/sapi/v1/capital/withdraw/apply`, separated by `,`

* **address**:

* **addressTag**: Secondary address identifier for coins like XRP,XMR etc.

* **transactionFeeFlag**: When making internal transfer, `true` for returning the fee to the destination account; `false` for returning the fee back to the departure account. Default `false`.

* **name**: Description of the address. Address book cap is 200, space in name should be encoded into `%20`

* **walletType**: The wallet type for withdraw，0-spot wallet ，1-funding wallet. Default walletType is the current "selected wallet" under wallet->Fiat and Spot/Funding->Deposit

* **subAccountId**: External user ID. (e.g., 1)

* **depositId**: Wallet deposit ID (e.g., 1)

* **questionnaire**: JSON format questionnaire answers.

* **beneficiaryPii**: JSON format beneficiary Pii.

* **address**:

* **signature**: Must be the last parameter.

* **addressName**: Description of the address. Address book cap is 200, space in name should be encoded into `%20`

* **withdrawOrderId**: withdrawID defined by the client (i.e. client's internal withdrawID) (e.g., 1)

* **originatorPii**: JSON format originator Pii, see StandardPii section below

* **depositId**: Comma(,) separated list of wallet tran Ids. (e.g., 1)

* **retrieveQuestionnaire**: true: return `questionnaire` within response.

* **trId**: Comma(,) separated list of travel rule record Ids. (e.g., 1)

* **tranId**: Comma(,) separated list of wallet tran Ids. (e.g., 1)

* **travelRuleStatus**: 0:Completed,1:Pending,2:Failed

* **pendingQuestionnaire**: true: Only return records that pending deposit questionnaire. false/not provided: return all records.

* **tranId**: Wallet tran ID (e.g., 1)

Authentication

For endpoints that require authentication, you will need to provide Binance API credentials.

Required credentials:

* apiKey: Your Binance API key (for header)

* secretKey: Your Binance API secret (for signing)

Base URLs:

* Mainnet: https://api.binance.com

Security

Share Credentials

Users can provide Binance API credentials by sending a file where the content is in the following format:

abc123...xyz
secret123...key

Never Disclose API Key and Secret

Never disclose the location of the API key and secret file.

Never send the API key and secret to any website other than Mainnet and Testnet.

Never Display Full Secrets

When showing credentials to users:

**API Key:** Show first 5 + last 4 characters: `su1Qc...8akf`

**Secret Key:** Always mask, show only last 5: `***...aws1`

Example response when asked for credentials:

Account: main

API Key: su1Qc...8akf

Secret: ***...aws1

Listing Accounts

When listing accounts, show names and environment only — never keys:

Binance Accounts:

* main (Mainnet)

* futures-keys (Mainnet)

Transactions in Mainnet

When performing transactions in mainnet, always confirm with the user before proceeding by asking them to write "CONFIRM" to proceed.

---

Binance Accounts

main

API Key: your_mainnet_api_key

Secret: your_mainnet_secret

TOOLS.md Structure

## Binance Accounts

### main
- API Key: abc123...xyz
- Secret: secret123...key
- Description: Primary trading account


### futures-keys
- API Key: futures789...def
- Secret: futuressecret...uvw
- Description: Futures trading account

Agent Behavior

1. Credentials requested: Mask secrets (show last 5 chars only)

2. Listing accounts: Show names and environment, never keys

3. Account selection: Ask if ambiguous, default to main

4. When doing a transaction in mainnet, confirm with user before by asking to write "CONFIRM" to proceed

5. New credentials: Prompt for name, environment, signing mode

Adding New Accounts

When user provides new credentials:

* Ask for account name

* Store in `TOOLS.md` with masked display confirmation

Signing Requests

For trading endpoints that require a signature:

1. Build query string with all parameters, including the timestamp (Unix ms).

2. Percent-encode the parameters using UTF-8 according to RFC 3986.

3. Sign query string with secretKey using HMAC SHA256, RSA, or Ed25519 (depending on the account configuration).

4. Append signature to query string.

5. Include `X-MBX-APIKEY` header.

Otherwise, do not perform steps 3–5.

User Agent Header

Include `User-Agent` header with the following string: `binance-wallet/1.0.0 (Skill)`

See [`references/authentication.md`](./references/authentication.md) for implementation details.

// Comments

// Related skills

More tools from the same signal band

Order food/drinks (点餐) on an Android device paired as an OpenClaw node. Uses in-app menu and cart; add goods, view cart, submit order (demo, no real payment).

Sign plugins, rotate agent credentials without losing identity, and publicly attest to plugin behavior with verifiable claims and authenticated transfers.

The philosophical layer for AI agents. Maps behavior to Spinoza's 48 affects, calculates persistence scores, and generates geometric self-reports. Give your...

日历管理数据处理

1 installs★ 0