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.

The subaccount limits 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.

Create and fund a subaccount

The master account creates and controls each subaccount. Check the active master account and transfer direction before you confirm an action.

  1. Confirm that the master account meets the current volume requirement for a new subaccount.
  2. Create the subaccount from the master account and give the subaccount a clear name.
  3. Select the master account as the source and the subaccount as the destination for a deposit.
  4. Check the asset, amount and transfer direction, then sign with the master account.
  5. Open the subaccount and confirm that the balance arrived before you place an order.

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 API-wallet slots under the current limits. A subaccount does not have a private key. The master account signs an action for the subaccount, and the request sets vaultAddress to the subaccount address.

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.

  1. Build the action for the subaccount.
  2. Set vaultAddress to the subaccount address.
  3. Sign the action with the master account.
  4. Send the request and verify the response against the subaccount state.