Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Subaccounts

Subaccounts let one owner run separate trading strategies without mixing their assets, positions, or orders. A master account and its subaccounts form one account family.

How they work

  • Each subaccount has its own token balances, positions, orders, and margin checks.
  • USDC is eligible collateral. PRCL does not contribute to trading collateral.
  • Trading losses in one subaccount do not draw collateral from another subaccount or from the master account.
  • Tokens move between existing personal accounts through Transfer. Transfers have no fee and need no recipient approval.
  • Bridge deposits credit the master account. Move assets to a subaccount after the deposit is complete.
  • Withdrawals leave from the master account. Move assets back to the master before withdrawing.

An agent key approved on the master can trade the complete family. An agent approved on one subaccount can trade only that subaccount. Agent keys cannot create or close subaccounts or move collateral.

Fees

A master and its subaccounts form one family. Every account in the family pays the trading fee tier the family's combined trailing 30-day volume earns. See fees.

Availability

Subaccount capacity is based on the family's lifetime trading volume: the master's own trades plus its subaccounts' trades. The app shows the current capacity and progress toward the next subaccount. The first $100,000 unlocks 10 subaccounts. Each additional $100 million unlocks one, up to 50. The 11th requires $100.1 million. New subaccount is available while the number of existing subaccounts is below the unlocked capacity.

Manage subaccounts in the app

Open Accounts in the trading app. Expand an account to see its assets, total balance, available balance, and collateral eligibility. Available USDC excludes funds reserved for positions and orders. Available PRCL excludes staked and unbonding funds. Staking holdings appear with Master only.

Select the vertical three-dot menu to rename an account or close a subaccount. Closing a subaccount returns all remaining tokens to its Master in the same transaction. Open positions, orders, pending withdrawals, or negative balances block closure. The account ID cannot be reused. Master and vault accounts cannot be closed from this menu. The Active badge identifies the account selected for trading.

Personal Master offers Deposit, Withdraw, and Transfer. Subaccounts only offer Transfer. Vault funding and redemption use the vault interface; vault-family transfers stay within that family. See community vaults.

Manage subaccounts through the API

API-key requests use POST /tx/sign-and-submit. The transaction bodies are:

Create a subaccount
{
  "CreateSubaccount": {
    "master_account_id": 27
  }
}
Transfer tokens
{
  "Transfer": {
    "from_account_id": "27",
    "to_account_id": "31",
    "token_id": 0,
    "amount": "50000000"
  }
}

token_id identifies the asset: 0 is USDC and 1 is PRCL. Both use six decimal places, so "50000000" is 50 tokens. Read precision from GET /v1/tokens for other registered tokens. Transfer account IDs and amounts must be decimal strings. Amounts must be positive and fit within a signed 128-bit integer.

The destination must exist and be active. Transfers between personal accounts can cross owners. A vault-family transfer must stay within that vault family. A USDC transfer must leave enough collateral for positions and open orders. Hosted owner API keys can transfer; agent keys cannot.

In the app, username and wallet lookup select the recipient's personal Master. An explicit account ID selects that personal account. Review the destination before signing. Profile > Transfers shows incoming, outgoing, and own-account moves, including returns when a subaccount closes. This history starts with the generic transfer release.

Close a subaccount
{
  "CloseSubaccount": {
    "account_id": 31
  }
}

Wrap one action in the standard signed envelope described in Transactions. These capital-management actions require the account owner. They are not available to an agent key.