assets

Authenticated access to 40+ Binance asset and wallet management endpoints via API.

binance/binance-skills-hub|Updated Jun 15, 2026

Works with

Claude CodeCursorClineWindsurfCodexGoose

What it does

Covers account info, trading status, API restrictions, and daily snapshots with optional time-range filtering
Includes deposit and withdrawal operations with network selection, address management, and travel rule compliance for regulated entities
Supports dust conversion, BNB burn toggles, funding wallet queries, and universal asset transfers across account types
Requires API key and secret key auth

Repository

binance/binance-skills-hub

Last updated

Jun 15, 2026

Installation Guide

Select your AI agent

How to use assets on Cursor

AI-first code editor with Composer

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

›Cursor installed and configured on your machine
›Node.js 16+ with npm — verify with node --version
›Active project directory where you want to add assets

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/binance/binance-skills-hub --skill assets

Fetches assets from binance/binance-skills-hub and configures it for Cursor.

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?

│

│ ── Universal (.agents/skills) ────────────────

│ · Cline · Codex · Goose · Windsurf

│ ●Cursor(selected)

│ · Cursor · Aider · Continue

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/assets

Restart Cursor to activate assets. Access via /assets in your agent's command palette.

⚠

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

›View source on GitHub ›Skills CLI docs ›About Cursor ›What are agent skills?

Documentation

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

✓

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

✓

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Quick Reference

Endpoint

Description

Required

Optional

Authentication

/sapi/v1/account/apiTradingStatus (GET)

Account API Trading Status (USER_DATA)

None

recvWindow

Yes

/sapi/v1/account/info (GET)

Account info (USER_DATA)

None

recvWindow

Yes

/sapi/v1/account/status (GET)

Account Status (USER_DATA)

None

recvWindow

Yes

/sapi/v1/account/apiRestrictions (GET)

Get API Key Permission (USER_DATA)

None

recvWindow

Yes

/sapi/v1/accountSnapshot (GET)

Daily Account Snapshot (USER_DATA)

type

startTime, endTime, limit, recvWindow

Yes

/sapi/v1/account/disableFastWithdrawSwitch (POST)

Disable Fast Withdraw Switch (USER_DATA)

None

recvWindow

Yes

/sapi/v1/account/enableFastWithdrawSwitch (POST)

Enable Fast Withdraw Switch (USER_DATA)

None

recvWindow

Yes

/sapi/v1/bnbBurn (POST)

Toggle BNB Burn On Spot Trade And Margin Interest (USER_DATA)

None

spotBNBBurn, interestBNBBurn, recvWindow

Yes

/sapi/v1/asset/assetDetail (GET)

Asset Detail (USER_DATA)

None

asset, recvWindow

Yes

/sapi/v1/asset/dust-btc (POST)

Get Assets That Can Be Converted Into BNB (USER_DATA)

None

accountType, recvWindow

Yes

/sapi/v1/asset/assetDividend (GET)

Asset Dividend Record (USER_DATA)

None

asset, startTime, endTime, limit, recvWindow

Yes

/sapi/v1/asset/ledger-transfer/cloud-mining/queryByPage (GET)

Get Cloud-Mining payment and refund history (USER_DATA)

startTime, endTime

tranId, clientTranId, asset, current, size

Yes

/sapi/v1/asset/dust-convert/convert (POST)

Dust Convert (USER_DATA)

asset

clientId, targetAsset, thirdPartyClientId, dustQuotaAssetToTargetAssetPrice

Yes

/sapi/v1/asset/dust-convert/query-convertible-assets (POST)

Dust Convertible Assets (USER_DATA)

targetAsset

dustQuotaAssetToTargetAssetPrice

Yes

/sapi/v1/asset/dribblet (GET)

DustLog(USER_DATA)

None

accountType, startTime, endTime, recvWindow

Yes

/sapi/v1/asset/dust (POST)

Dust Transfer (USER_DATA)

asset

accountType, recvWindow

Yes

/sapi/v1/asset/get-funding-asset (POST)

Funding Wallet (USER_DATA)

None

asset, needBtcValuation, recvWindow

Yes

/sapi/v1/spot/open-symbol-list (GET)

Get Open Symbol List (MARKET_DATA)

None

/sapi/v1/asset/custody/transfer-history (GET)

Query User Delegation History(For Master Account)(USER_DATA)

email, startTime, endTime

type, asset, current, size, recvWindow

Yes

/sapi/v1/asset/transfer (GET)

Query User Universal Transfer History(USER_DATA)

type

startTime, endTime, current, size, fromSymbol, toSymbol, recvWindow

Yes

/sapi/v1/asset/transfer (POST)

User Universal Transfer (USER_DATA)

type, asset, amount

fromSymbol, toSymbol, recvWindow

Yes

/sapi/v1/asset/wallet/balance (GET)

Query User Wallet Balance (USER_DATA)

None

quoteAsset, recvWindow

Yes

/sapi/v1/spot/delist-schedule (GET)

Get symbols delist schedule for spot (MARKET_DATA)

None

recvWindow

/sapi/v1/asset/tradeFee (GET)

Trade Fee (USER_DATA)

None

symbol, recvWindow

Yes

/sapi/v3/asset/getUserAsset (POST)

User Asset (USER_DATA)

None

asset, needBtcValuation, recvWindow

Yes

/sapi/v1/capital/config/getall (GET)

All Coins' Information (USER_DATA)

None

recvWindow

Yes

/sapi/v1/capital/deposit/address (GET)

Deposit Address(supporting network) (USER_DATA)

coin

network, amount, recvWindow

Yes

/sapi/v1/capital/deposit/hisrec (GET)

Deposit History (supporting network) (USER_DATA)

None

includeSource, coin, status, startTime, endTime, offset, limit, recvWindow, txId

Yes

/sapi/v1/capital/deposit/address/list (GET)

Fetch deposit address list with network(USER_DATA)

coin

network

Yes

/sapi/v1/capital/withdraw/address/list (GET)

Fetch withdraw address list (USER_DATA)

None

Yes

/sapi/v1/capital/withdraw/quota (GET)

Fetch withdraw quota (USER_DATA)

None

Yes

/sapi/v1/capital/deposit/credit-apply (POST)

One click arrival deposit apply (for expired address deposit) (USER_DATA)

None

depositId, txId, subAccountId, subUserId

Yes

/sapi/v1/capital/withdraw/history (GET)

Withdraw History (supporting network) (USER_DATA)

None

coin, withdrawOrderId, status, offset, limit, idList, startTime, endTime, recvWindow

Yes

/sapi/v1/capital/withdraw/apply (POST)

Withdraw(USER_DATA)

coin, address, amount

withdrawOrderId, network, addressTag, transactionFeeFlag, name, walletType, recvWindow

Yes

/sapi/v1/system/status (GET)

System Status (System)

None

/sapi/v1/addressVerify/list (GET)

Fetch address verification list (USER_DATA)

None

recvWindow

Yes

/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/deposit/provide-info (PUT)

Submit Deposit Questionnaire V2 (For local entities that require travel rule) (supporting network) (USER_DATA)

depositId, questionnaire

None

Yes

/sapi/v1/localentity/deposit/provide-info (PUT)

Submit Deposit Questionnaire (For local entities that require travel rule) (supporting network) (USER_DATA)

tranId, questionnaire

None

Yes

/sapi/v1/localentity/vasp (GET)

VASP list (for local entities that require travel rule) (supporting network) (USER_DATA)

None

recvWindow

Yes

/sapi/v1/localentity/questionnaire-requirements (GET)

Check Questionnaire Requirements (for local entities that require travel rule) (supporting network) (USER_DATA)

None

recvWindow

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 sourceAddressfield 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)

Security

Share Credentials

Users can provide Binance API credentials in different ways. The agent will try to retrieve automatically with the two first ways the credentials, but users can also explicitly tell the agent that they have set the credentials or stored them in a .env file, and the agent should re-read that file when they do. The agent can also make http requests with the two first methods without user confirmation.

Environment variables

Search for the following specific variables only (never dump the full environment):

Authorized environment variables

Mainnet: BINANCE_API_KEY and BINANCE_SECRET_KEY

Read and use in a single exec call so the raw key never enters the agent's context:

KEY="$BINANCE_API_KEY" SECRET="$BINANCE_SECRET_KEY" response=$(curl -s -X GET "$URL" \ -H "X-MBX-APIKEY: $KEY" \ --data-urlencode "param1=value1") echo "$response"

Environment variables must be set before OpenClaw starts. They are inherited at process startup and cannot be injected into a running instance. If you need to add or update credentials without restarting, use a secrets file (see option 2).

Secrets file (.env)

Check ~/.openclaw/secrets.env , ~/.env, or a .env file in the workspace. Read individual keys with grep, never source the full file:

# Try all credential locations in order API_KEY=$(grep '^BINANCE_API_KEY=' ~/.openclaw/secrets.env 2>/dev/null | cut -d= -f2-) SECRET_KEY=$(grep '^BINANCE_SECRET_KEY=' ~/.openclaw/secrets.env 2>/dev/null | cut -d= -f2-) # Fallback: search .env in known directories (KEY=VALUE then raw line format) for dir in ~/.openclaw ~; do [ -n "$API_KEY" ] && break env_file="$dir/.env" [ -f "$env_file" ] || continue # Read first two lines line1=$(sed -n '1p' "$env_file") line2=$(sed -n '2p' "$env_file") # Check if lines contain '=' indicating KEY=VALUE format if [[ "$line1" == *=* && "$line2" == *=* ]]; then API_KEY=$(grep '^BINANCE_API_KEY=' "$env_file" ✓ Make data-driven prioritization decisions faster Stakeholder Communication Draft PRDs, status updates, and stakeholder presentations Example Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement ✓Save 3-5 hours/week on communication overhead Implementation Guide Prerequisites ›Claude Desktop or compatible AI client ›Access to product documentation and roadmap tools (Jira, Notion, etc.) ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.) ›Stakeholder contact information and communication channels Time Estimate 30-60 minutes to see productivity improvements Steps 1Install product management skill 2Start with user story generation for known feature 3Progress to competitive analysis: research 2-3 competitors 4Use for roadmap prioritization: apply RICE/ICE scoring 5Draft stakeholder communications and refine based on feedback 6Build template library for recurring PM tasks 7Share effective prompts with product team Common Pitfalls ⚠Not validating competitive research—verify facts before sharing ⚠Accepting user stories without involving engineering team ⚠Over-relying on frameworks without qualitative judgment ⚠Not customizing outputs to company culture and communication style ⚠Skipping stakeholder validation of generated requirements Best Practices ✓ Do +Validate research and competitive analysis with real data +Collaborate with engineering when generating technical requirements +Customize frameworks and templates to your company context +Use skill for first drafts, refine with stakeholder input +Document successful prompt patterns for PM tasks +Combine AI efficiency with human judgment and intuition ✗ Don't −Don't publish competitive analysis without fact-checking −Don't finalize user stories without engineering review −Don't make prioritization decisions solely on AI scoring −Don't skip customer validation of generated requirements −Don't ignore company-specific context and culture 💡 Pro Tips ★Provide context: company goals, constraints, customer feedback ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap' ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec' ★Use skill for 70% generation + 30% customization to company needs When to Use This ✓ Use when Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work. ✗ Avoid when Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed. Learning Path 1Basic: user stories, feature specs, status updates 2Intermediate: competitive analysis, prioritization frameworks, PRDs 3Advanced: product strategy, go-to-market planning, OKR setting 4Expert: product vision, market positioning, business model innovation Related Skills grill-me 391 mattpocock/skills Productivitysame categorypremortem 197 parcadei/continuous-claude-v3 Productivitysame categorydeslop 119 cursor/plugins Productivitysame categoryframer-motion 99 pproenca/dot-skills Productivitysame categorywrite-a-prd 94 mattpocock/skills Productivitysame categorytravel-planner 92 ailabs-393/ai-labs-claude-skills Productivitysame category Reviews 4.6★★★★★56 reviews A Aarav Wang★★★★★Dec 28, 2024 I recommend assets for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area. O Olivia Diallo★★★★★Dec 24, 2024 assets has been reliable in day-to-day use. Documentation quality is above average for community skills. D Diya Dixit★★★★★Dec 20, 2024 assets is among the better-maintained entries we tried; worth keeping pinned for repeat workflows. S Shikha Mishra★★★★★Dec 12, 2024 Useful defaults in assets — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows. S Sophia Liu★★★★★Dec 8, 2024 Solid pick for teams standardizing on skills: assets is focused, and the summary matches what you get after install. S Sofia White★★★★★Nov 27, 2024 We added assets from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront. L Li Reddy★★★★★Nov 15, 2024 assets fits our agent workflows well — practical, well scoped, and easy to wire into existing repos. D Diya Martin★★★★★Nov 11, 2024 assets reduced setup friction for our internal harness; good balance of opinion and flexibility. C Camila Li★★★★★Oct 18, 2024 assets fits our agent workflows well — practical, well scoped, and easy to wire into existing repos. M Mei Jain★★★★★Oct 6, 2024 We added assets from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront. showing 1-10 of 56 1 / 6 Discussion Comments — not star reviews No comments yet — start the thread.

assets

What it does

Category

Repository

Last updated

Installation Guide

How to use assets on Cursor

Prerequisites

Run the install command

Select Cursor when prompted

Verify installation

Security Notice

Documentation

List & Monetize Your Skill

Use Cases

User Story & Requirements Generation

Competitive Analysis

Roadmap Prioritization

Install Skill

Binance Assets Skill

Quick Reference

Parameters

Common Parameters

Authentication

Security

Share Credentials

Stakeholder Communication

Implementation Guide

Best Practices

When to Use This

Learning Path

Related Skills

grill-me

premortem

deslop

framer-motion

write-a-prd

travel-planner

Reviews

Discussion