sub-account

Create, configure, and query Binance sub-accounts via signed REST endpoints.

957|244|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/tradecatlabs/tradecat-public --skill sub-account-tradecatlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sub-account
Source: https://github.com/tradecatlabs/tradecat-public/tree/main/resources/agent_market_context/binance/upstream/binance-skills-hub-main/skills/binance/sub-account
Command: npx skills add https://github.com/tradecatlabs/tradecat-public --skill sub-account-tradecatlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Sub-account operations on Binance require authenticated, parameterized API calls, which is hard to do correctly and consistently without errors.

Core Features & Use Cases

  • Sub-account lifecycle and configuration: Create virtual sub-accounts and enable Futures or Options for them using authenticated endpoints.
  • Account and risk querying: Fetch sub-account status, margin account details, and Futures position-risk/account snapshots for monitoring and reporting.
  • Assets and transfer operations: Query sub-account assets and perform transfers (including margin/futures internal movements) using signed requests.

Quick Start

Ask the AI to enable Futures for a specific sub-account email by calling POST /sapi/v1/sub-account/futures/enable with your Binance API key/secret and return the JSON response.

Frequently Asked Questions about sub-account

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make authenticated Binance sub-account API requests?

Authenticated Binance sub-account API requests require an API key and secret to build signed query strings with timestamps. The Skill handles this by configuring and querying sub-account resources via REST endpoints, returning the result as formatted JSON.

How do I enable Futures or Options for a Binance sub-account via API?

To enable Futures or Options for a Binance sub-account, you make a POST request to the specific virtual sub-account endpoint. The Skill builds the authenticated signed request using your API key and secret, enabling the targeted virtual sub-account features.

Can I manage asset transfers between Binance master and sub-accounts programmatically?

Yes, you can manage asset transfers between master-managed sub-accounts, including margin and futures internal movements. The Skill executes these asset transfers by building signed requests with your Binance API credentials and returning the endpoint result as JSON.

Do I need a Binance API key and secret to query sub-account position risk?

Yes, a Binance API key and secret are required to query sub-account position risk and account summaries. The Skill uses these credentials to build signed query strings with timestamps, ensuring authenticated requests successfully return the JSON response.

Why do my Binance sub-account API calls fail without signed query strings?

Binance sub-account API calls fail without signed query strings because authenticated endpoints require timestamp and signature validation. The Skill resolves this by building properly signed requests using your API key and secret to fetch the JSON response.