> For the complete documentation index, see [llms.txt](https://help.topstepx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.topstepx.com/components/accounts.md). # Accounts The Accounts component provides an overview of all accounts associated with the user. ## Accounts Component The Accounts component provides a snapshot of all trading accounts associated with the user. It shows important details for each account, helping you keep track of your account's status throughout the trading day.
The Accounts component contains the following information: * **Status** - Indicates the current status of the account. Possible values are *Active*, *Temp. Liquidation*, *Goal Achieved*, and *Ineligible*. * **Created On** - Displays the date and time when the account was created. * **Account Name** - Lists the account name for each account. * **Win Rate** - Displays the percentage of winning trades out of total trades executed. * **Total Lots Traded** - Indicates the total number of lots traded from the account. * **Day P\&L** - Displays the realized profit and loss for the current trading day. * **Open P\&L** - Displays the unrealized profit and loss for open positions in real-time. * **Account Balance** - Displays the current balance of the account in real-time. To add Accounts to your layout, first add it as a [component](/components.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://help.topstepx.com/components/accounts.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.