> 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/trading.md).

# Trade on a funded account

After you win a funded account, open the funded **Terminal** to trade it under its rules.

## Open the Terminal

1. Open the funded **Terminal**.
2. Select an equipped funded account, or equip one from your **Inventory**.
3. Review its profit split, loss limits, and remaining loss allowance.
4. Choose a market and review its position and leverage limits.

A demo does not create a funded account or funded earnings.

## Monitor open positions

Equity is your balance plus profit or loss on open trades. Price changes can breach a loss limit while you're away.

Swap between equipped accounts in the funded Terminal. Positions on your other equipped accounts stay open when you switch. Monitor each account with open positions.

You cannot request a payout from an account with open positions. Close all of its positions first.

Trading costs reduce account performance. Your wallet balance stays separate from the account's capital.

See [Drawdown rules](/docs/funded/drawdown.md) before trading, and [Payouts](/docs/funded/payouts.md) to transfer eligible earnings.


---

# 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/trading.md?ask=<question>&goal=<user_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.