Creation limits depend on volume
The official documentation currently allows up to 10 subaccounts after the master account reaches $100,000 in volume. Each additional $100M in volume enables one more subaccount, up to a maximum of 50.
These are account permissions, not trading targets. Generating uneconomic volume only to unlock account slots can cost more in fees and slippage than the operational separation is worth.
What a subaccount separates
A subaccount is useful for isolating strategies, operators or reporting views without maintaining an unrelated signing identity for every workflow. Its clearinghouse state is independent even though the master controls actions on its behalf.
Portfolio-margin treatment remains separate by subaccount. Do not assume a profitable master balance will automatically protect a stressed subaccount.
Fee tier shared; referral discount excluded
Subaccount volume contributes to the master account’s fee tier, and the master plus subaccounts share that tier. The referral documentation separately states that referral discounts do not apply to subaccounts.
Model the tier benefit and referral exclusion as two independent rules. A lower volume-tier rate can still apply even when the additional 4% referred-user discount does not.
API wallets and signing
Master accounts start with three API wallets, and each subaccount adds two available API-wallet slots under the current limits. Actions for a subaccount are signed by the master account and identify the subaccount through the relevant address field.
Apply least privilege, separate secrets by environment and strategy, and test cancel or shutdown behavior. A convenient account hierarchy does not replace key rotation and incident response.