> For the complete documentation index, see [llms.txt](https://docs.tradesurge.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradesurge.co/platform/accounts.md).
# Accounts
An Account is one trading account at one prop firm. It holds that firm's rules, your phase and your risk dial.
An Account is one trading account at one prop firm. It holds the firm's rules, your phase, your account size and your risk dial. Every other part of TradeSurge, from the Terminal to Breach Guard, reads from it.
## Add an account in four steps
The add-account wizard walks you through **Venue → Account → Keys → Done**. You pick where the account lives, fill in its facts, paste a trade-scoped key, and the account is ready. You can skip the key and register it later, but the Terminal stays read-only for that account until a key is on the engine.
## What an account holds
| Name | What it means |
| ---------------- | -------------------------------------------------------------------------------------- |
| **Label** | Your name for the account, for example "FundedNext Eval". |
| **Firm** | The prop firm, picked from the Firm Catalogue. The firm sets the Rules & Limits. |
| **Phase** | Evaluation (Phase 1 or Phase 2) or Funded. The phase changes what Profit Target means. |
| **Account size** | The starting balance the firm gives you. |
| **Risk dial** | Your risk per trade, as a percent. The engine sizes every trade within it. |
| **Status** | Whether the account is active. |
## Rules come from the firm, not from you
When you pick a firm, TradeSurge loads that firm's daily drawdown, maximum drawdown, profit target and daily reset. You see them as progress bars on the account's **Rules & Limits** tab. If a firm's limit is not confirmed in the catalogue, TradeSurge marks it "Limit unconfirmed" and blocks new entries rather than guess.
## Why accounts come first
Scaling one strategy across more accounts only works if each account is sized and protected on its own terms. The Account is where those terms live, so one order can become many correctly sized orders.
## Next steps
---
# 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://docs.tradesurge.co/platform/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.