Sub Account
Let an agent call Binance Sub-account REST endpoints with correct signing when you are wiring trading, treasury, or multi-account automation.
Overview
Sub-account is an agent skill for the Build phase that performs authenticated Binance Sub-account API requests using API key and secret credentials.
Install
npx skills add https://github.com/binance/binance-skills-hub --skill sub-accountWhat is this skill?
- Guides Binance Sub-account API requests with API key and secret authentication
- Supports credentials from environment variables or credential files (v1.1.0)
- Handles signature generation for RSA and Ed25519 API key types
- Sets User Agent metadata including Openclaw per hub changelog
- Hub version 1.1.0 (2026-03-24) adds env/file credential input and RSA and Ed25519 signature fixes
- Initial hub release 1.0.0 dated 2026-03-19
Adoption & trust: 1.1k installs on skills.sh; 881 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need Binance sub-account operations in your agent workflow but do not want to reimplement signing, key formats, and auth setup on every invocation.
Who is it for?
Solo builders integrating Binance sub-account management into bots, internal tools, or agent workflows with stored API credentials.
Skip if: Teams that only need spot or futures on a single master account with no sub-account model, or builders who want a hosted MCP server instead of a skill package.
When should I use this skill?
You need Binance Sub-account API calls and have API key plus secret key available via env, files, or secure agent context.
What do I get? / Deliverables
Your agent can call Sub-account endpoints with keys from env or files and signatures that match RSA or Ed25519 Binance key types.
- Authenticated Sub-account API request patterns the agent can execute
- Correctly signed requests for the configured RSA or Ed25519 key type
Recommended Skills
Journey fit
Sub-account API work is integration plumbing you add while building a product that talks to Binance, not a launch or growth tactic. The skill centers on authenticated HTTP to Binance Sub-account APIs—classic third-party integration work in the build phase.
How it compares
Use as a focused Binance Sub-account skill package rather than generic REST examples that omit Ed25519/RSA signing details.
Common Questions / FAQ
Who is sub-account for?
Indie developers and small teams building agent-driven or scripted tools that must create, query, or manage Binance sub-accounts via the official API.
When should I use sub-account?
Use it during Build integrations when you wire Sub-account endpoints, rotate keys from env or files, or debug signature errors for RSA or Ed25519 Binance keys.
Is sub-account safe to install?
Treat it like any third-party skill that touches API secrets: review the Security Audits panel on this Prism page, restrict key permissions on Binance, and never commit live credentials to git.
SKILL.md
READMESKILL.md - Sub Account
# 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-19 - 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: sub-account description: Binance Sub-account 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/sub-account/SKILL.md license: MIT --- # Binance Sub-account Skill Sub-account 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/sub-account/virtualSubAccount` (POST) | Create a Virtual Sub-account (For Master Account) (USER_DATA) | subAccountString | recvWindow | Yes | | `/sapi/v1/sub-account/futures/enable` (POST) | Enable Futures for Sub-account (For Master Account) (USER_DATA) | email | recvWindow | Yes | | `/sapi/v1/sub-account/eoptions/enable` (POST) | Enable Options for Sub-account (For Master Account) (USER_DATA) | email | recvWindow | Yes | | `/sapi/v2/sub-account/futures/positionRisk` (GET) | Get Futures Position-Risk of Sub-account V2 (For Master Account) (USER_DATA) | email, futuresType | recvWindow | Yes | | `/sapi/v1/sub-account/futures/positionRisk` (GET) | Get Futures Position-Risk of Sub-account (For Master Account) (USER_DATA) | email | recvWindow | Yes | | `/sapi/v1/sub-account/status` (GET) | Get Sub-account's Status on Margin Or Futures (For Master Account) (USER_DATA) | None | email, recvWindow | Yes | | `/sapi/v1/sub-account/list` (GET) | Query Sub-account List (For Master Account) (USER_DATA) | None | email, isFreeze, page, limit, recvWindow | Yes | | `/sapi/v1/sub-account/transaction-statistics` (GET) | Query Sub-account Transaction Statistics (For Master Account) (USER_DATA) | None | email, recvWindow | Yes | | `/sapi/v2/sub-account/subAccountApi/ipRestriction` (POST) | Add IP Restriction for Sub-Account API key (For Master Account) (USER_DATA) | email, subAccountApiKey, status | ipAddress, recvWindow | Yes | | `/sapi/v1/sub-account/subAccountApi/ipRestriction/ipList` (DELETE) | Delete IP List For a Sub-account API Key (For Master Account) (USER_DATA) | email, subAccountApiKey, ipAddress | recvWindow | Yes | | `/sapi/v1/sub-account/subAccountApi/ipRestriction` (GET) | Get IP Restriction for a Sub-account API Key (For Master Account) (USER_DATA) | email, subAccountApiKey | recvWindow | Yes | | `/sapi/v1/sub-account/futures/transfer` (POST) | Futures Transfer for Sub-account (For Master Acco