> For the complete documentation index, see [llms.txt](https://www.aevo.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.aevo.xyz/docs/aevo-products/aevo-exchange/subaccounts.md). # Subaccounts Subaccounts let you split your trading into separate accounts under one wallet. Each subaccount has its own balance, positions and margin, so you can run different strategies side by side, or keep a bot away from your main funds, without connecting another wallet. You connect your wallet and sign in once. After that you can create subaccounts, switch between them and move funds, all from the same session. *** ## How subaccounts work * **Main account.** The account of the wallet you connect. It owns every subaccount you create. * **Subaccount.** A separate trading account linked to your main account. It has its own address, balances, positions, orders and margin. * **Separate risk.** Margin and liquidation are calculated for each account on its own. A loss on one subaccount cannot use the collateral of your main account or of another subaccount, and a liquidation on one account does not touch the others. * **One login.** Your main account's sign-in and keys work for all of your subaccounts. See [Subaccounts in the API reference](/docs/api-reference/subaccounts.md) for API trading. *** ## Creating and switching 1. Open the account menu (your address at the top right) and select **Sub-accounts**. You can also go to **Settings → Subaccounts**. 2. Enter a name and select **Create**. Names are 1 to 16 characters long and may use letters, numbers, spaces, underscores and hyphens. Each name must be unique among your active subaccounts. 3. Your wallet asks for one signature the first time you create a subaccount in a session. It is free and doesn't send a transaction. To switch, open **Sub-accounts** and select the account you want to trade on. The account button shows a **SUB** tag and the subaccount's name while you're trading as a subaccount, and a **MAIN** tag when you're on your main account. Each wallet can have up to **10 active subaccounts**. Archived subaccounts don't count toward this limit. {% hint style="info" %} Your subaccounts are tied to your wallet. Signing in with the same wallet on another device shows the same subaccounts. {% endhint %} *** ## Moving funds | | Main account | Subaccount | | ---------------------- | ----------------------------------------------- | ------------------------------------------------------------------ | | **Deposit** | Yes | Deposit to your main account, then transfer | | **Receive a transfer** | From any Aevo account | **Only from your main account or another of your subaccounts** | | **Transfer** | To any Aevo account, including your subaccounts | **Only to your main account or another of your subaccounts** | | **Withdraw** | Yes | **Never.** Transfer to your main account, then withdraw from there | * To fund a subaccount, switch to your main account and use **Transfer**. Your subaccounts appear as quick picks. Other people can't transfer to your subaccounts. * To move funds out of a subaccount, use **Transfer** while the subaccount is active and pick your main account or another of your subaccounts. * To withdraw funds held in a subaccount, transfer them to your main account first, then withdraw from your main account. *** ## Fees, volume and rewards * **Trading fees** are set by your main account. Your fee tier, staking discount and any custom fees apply to every subaccount. * **Volume** from all of your subaccounts counts toward your main account. It is combined for your staking tier, volume-based cashback and trading-fee campaigns. * **Rewards are paid to your main account.** Cashback and campaign rewards earned through subaccount trading are paid to your main account. Subaccounts can't claim rewards themselves. * **Leaderboards** show your main wallet once, with the combined volume of the main account and all of its subaccounts. * **Builder codes.** A subaccount can approve builders and trade through them, but it can't register as a builder. Register builders from your main account. * **Referrals don't apply to subaccounts.** A subaccount can't use or own a referral code, and trading on a subaccount doesn't earn referral rewards or referee discounts. Referrals stay on your main account. *** ## Trading between your own accounts Your main account and its subaccounts can never trade against each other. If an order would fill against another of your own accounts, the incoming order is cancelled instead. This applies to the order book and to RFQ / block trades. *** ## Archiving a subaccount You can archive a subaccount you no longer use in **Settings → Subaccounts**. It must be empty first: no balances, positions, open orders or pending withdrawals. Archiving frees a slot under your subaccount limit. An archived subaccount can't be used for trading or receive transfers. *** ## FAQ **Does a subaccount need its own wallet?** No. Subaccounts are created and controlled by your main wallet. You don't need to install, fund or back up anything else. **Can I use the API with subaccounts?** Yes. Your main account's API key can trade any of your subaccounts: add the `AEVO-SUBACCOUNT` header with the subaccount's address to each request, and set the order's `maker` to that address. See [Trading with a subaccount](/docs/api-reference/subaccounts/trading-with-subaccounts.md) for complete examples. **If my main account is restricted, are my subaccounts affected?** Yes. Any restriction on your main account also applies to all of its subaccounts. **Why can't I withdraw from a subaccount?** Funds leave Aevo only through your main account. Transfer from the subaccount to your main account, then withdraw. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.aevo.xyz/docs/aevo-products/aevo-exchange/subaccounts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.