> 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/getting-started/readme.md).

# What is TradeSurge?

TradeSurge is an AI-native trading operating system for prop traders who already have an edge and want to scale it across more funded accounts.

TradeSurge is a trading operating system for prop traders who already have an edge. It takes one strategy you believe in and runs it across every funded account you hold, with less manual work and fewer execution errors. You own the edge and the decisions. TradeSurge handles the operations around them.

{% hint style="info" %}
**Early access.** TradeSurge is in invite-only alpha. Trading will open on Bybit demo accounts first, for invited traders.
{% endhint %}

## The problem it solves

A strategy that works on one account gets harder to run on three, five or ten. You copy every trade by hand, size each one separately, watch a different drawdown limit on each firm, and track results in a spreadsheet. One missed rule ends an account. TradeSurge puts all of that into one cockpit.

## How you use it

TradeSurge follows one loop: **prepare, execute, review, refine.**

* **Prepare.** Connect your accounts, set each firm's rules and your risk per trade.
* **Execute.** Send one order to every selected account, each copy sized in R for that account.
* **Review.** See every account, every trade and every rule in one place, measured in R.
* **Refine.** Journal, analyse and adjust the strategy, then scale it to more accounts.

## SurgeAI

SurgeAI is the trading copilot coming to TradeSurge (coming soon). You will describe your edge in plain language, and SurgeAI will help turn it into a structured strategy, backtest it and, later, deploy it as a trading agent. See [SurgeAI](/platform/surgeai.md).

## The free toolkit

`tradesurge.co` also has free tools that need no account: an Eval Simulator, calculators and a prop-firm directory. They are a useful first stop before you buy a challenge.

## Who it is for

TradeSurge is built for traders running three or more funded or evaluation accounts. It starts with crypto prop firms on Bybit rails, then adds MetaTrader 5 and MatchTrader firms.

## Pick your side

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Scale my accounts</strong></td><td>Connect a prop account and take your first R-sized trade.</td><td><a href="/platform/platform.md">Platform overview</a></td></tr><tr><td><strong>Try the free tools</strong></td><td>Check your odds of passing before you pay for a challenge.</td><td><a href="/free-tools/free-tools.md">Free tools overview</a></td></tr></tbody></table>


---

# 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/getting-started/readme.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.
