Assets
Call Binance Assets API endpoints from an agent with correct signing (including RSA/Ed25519), env-based keys, and versioned hub metadata for trading or portfolio tooling.
Overview
Assets is an agent skill for the Build phase that performs Binance Assets API calls with API key and secret authentication and current signing behavior.
Install
npx skills add https://github.com/binance/binance-skills-hub --skill assetsWhat is this skill?
- Binance Assets API requests with API key and secret authentication (metadata v1.1.0)
- v1.1.0: environment variables or files for API key and secret input
- v1.1.0: signature generation fixes for RSA and Ed25519 keys
- User-Agent includes Openclaw metadata per changelog
- MIT-licensed Binance hub skill with documented 1.0.0 initial and 1.1.0 env/signature release notes
- Skill metadata version 1.1.0 (2026-03-24 changelog)
- Initial release 1.0.0 (2026-03-10)
Adoption & trust: 2k installs on skills.sh; 881 GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are wiring Binance asset data into your app but agent-generated API code keeps breaking on signatures, key types, or secret handling.
Who is it for?
Developers building Binance-connected dashboards, bots, or internal tools who already have Binance API keys and want a skill-shaped integration guide.
Skip if: Non-crypto products, paper trading without real keys, or users who cannot legally use Binance APIs in their jurisdiction—use mocks instead.
When should I use this skill?
You need Binance Assets API requests with API key and secret authentication in an agent session.
What do I get? / Deliverables
Your agent follows the hub’s Assets request patterns with env/file credentials and corrected RSA/Ed25519 signing so integrations compile and authenticate predictably.
- Authenticated Assets API request implementations
- Correct signature generation for configured key type
Recommended Skills
Journey fit
Build → integrations is the primary shelf because the skill encapsulates authenticated HTTP integration to Binance—not live ops monitoring by itself. Assets API wiring is classic third-party financial integration work during product construction.
How it compares
A finance API integration skill, not a generic REST template or on-chain Web3 wallet skill.
Common Questions / FAQ
Who is assets for?
Solo builders and small teams implementing Binance Assets API features inside agent-driven development workflows.
When should I use assets?
During build when integrating portfolio or asset endpoints; during operate when extending an existing Binance-connected service—always with scoped API keys and human review for money-moving actions.
Is assets safe to install?
It requires exchange API secrets and live network calls; review the Security Audits panel on this Prism page, use read-only keys where possible, and never commit credentials.
SKILL.md
READMESKILL.md - Assets
# Changelog ## 1.1.0 - 2026-03-24 - Environmental variables or files can now be used as input for the API key and secret key. - Fix signature generation for RSA and Ed25519 keys. - Add `Openclaw` metadata to the User Agent header ## 1.0.0 - 2026-03-10 - Initial release MIT License Copyright (c) 2026 Binance Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. --- name: assets description: Binance Assets request using the Binance API. Authentication requires API key and secret key. metadata: version: 1.1.0 author: Binance openclaw: requires: bins: - curl - openssl - date homepage: https://github.com/binance/binance-skills-hub/tree/main/skills/binance/assets/SKILL.md 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 | 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` (