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

# Quickstart

TradeSurge has two sides, so it has two starting points.

TradeSurge has two sides, so it has two starting points. First, decide which side you are on. Then follow the matching steps below.

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

## If you want to run your accounts

{% stepper %}
{% step %}

### Sign in

Go to `app.tradesurge.co` and sign in with Google or a magic link. Choose a handle.
{% endstep %}

{% step %}

### Turn on two-factor

You must enrol an authenticator app to use the app. A second-factor check at sign-in and before key changes is coming before live trading.
{% endstep %}

{% step %}

### Add an account

Pick the venue, the firm, the phase, the account size and your risk per trade. See [Accounts](/platform/accounts.md).
{% endstep %}

{% step %}

### Paste a trade-scoped key

Create a Bybit API key with trade permission and withdrawals disabled. TradeSurge checks the key's permissions and refuses it if withdrawals are allowed. See [Trade-scoped keys](/platform/accounts/trade-scoped-keys.md).
{% endstep %}

{% step %}

### Take your first trade

Open the Terminal, choose your accounts and enter a trade. Every order is sized in R and carries a stop that rests on the exchange.
{% endstep %}
{% endstepper %}

## If you want the free tools

{% stepper %}
{% step %}

### Open the Eval Simulator

Go to `tradesurge.co/simulator`. No sign-in is needed.
{% endstep %}

{% step %}

### Enter your numbers

Enter your win rate, average win and average loss in R, and trades per day. Pick the firm and challenge you are considering.
{% endstep %}

{% step %}

### Read your odds

The simulator runs 1,000 paths and shows your chance to pass, your chance to breach and the days it usually takes.
{% endstep %}
{% endstepper %}

## Next steps

<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>How TradeSurge works</strong></td><td>The four building blocks behind every screen.</td><td><a href="/getting-started/how-tradesurge-works.md">How TradeSurge works</a></td></tr><tr><td><strong>Connect Bybit</strong></td><td>Add your first account step by step.</td><td><a href="/platform/accounts/connect-bybit.md">Connect Bybit</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/quickstart.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.