> For the complete documentation index, see [llms.txt](https://www.size.club/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.size.club/docs/funded/choose-an-account.md). # Choose a funded account Choose the funded account size you want to win. Each size has a set entry price. Finish first to win the selected account. The entry price pays for an attempt, not a guaranteed account. ## Review the account Before entering, check: * Entry price. * Funded account size. * Your share of profits. * Daily and total loss limits. The account size is trading capital. You can receive your eligible share of profits through a payout. Starting capital cannot be withdrawn. ## Enter the game Select an account size, review the entry price and reward, then confirm your entry. If your game result is missing, [contact support](/docs/help/support.md) with the game ID, entry details, and time. ## Accounts you already hold Each account keeps its own size, profit split, and loss limits. A new offer does not change an existing account. After a win, open the funded **Terminal**, select your account, and trade under its rules. You can swap between equipped accounts there. See [Manage funded accounts](/docs/funded/manage-accounts.md). --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.size.club/docs/funded/choose-an-account.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 `automate deployments from our CI pipeline` 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.