> 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/connect-bybit.md).
# Connect Bybit
Connect a Bybit-rail prop account with a trade-scoped API key.
Bybit is the first venue TradeSurge supports. Most crypto prop firms run their accounts on Bybit rails, so this is where you start. This page takes you from a new account to a registered key.
{% hint style="info" %}
**Early access.** Connecting Bybit opens on demo accounts first, for invited traders.
{% endhint %}
## What you need
* A TradeSurge login with two-factor turned on.
* A Bybit or Bybit-rail prop account.
* A new API key and secret with trade permission and withdrawals turned off.
## Connect the account
{% stepper %}
{% step %}
### Choose the venue
Open **Accounts**, select **Add account** and pick **Bybit**.
{% endstep %}
{% step %}
### Fill in the account
Enter a label, then pick the firm, the phase, the account size and your risk dial.
{% endstep %}
{% step %}
### Create a trade-scoped key
In Bybit, create an API key with contract and order (trade) permission. Leave withdrawal and transfer turned off.
{% endstep %}
{% step %}
### Paste the key and secret
Paste both into the **Keys** step. TradeSurge asks Bybit what the key can do before accepting it.
{% endstep %}
{% step %}
### Confirm the account is ready
When the checks pass, you see **Account ready**. The account now appears in the Terminal and on the Dashboard.
{% endstep %}
{% endstepper %}
{% hint style="warning" %}
The most common failure is a key with withdrawals turned on. TradeSurge will never accept a withdrawal-capable key. Create a new trade-only key and paste that instead.
{% endhint %}
## Good to know
* Every entry carries a stop that rests on Bybit, so your protection survives even if TradeSurge goes offline.
* If you skip the key, register it later from the account page.
* If Bybit rejects the key, check that it is correct, active and not IP-restricted away from the engine.
* See [Trade-scoped keys](/platform/accounts/trade-scoped-keys.md) for every rejection reason.
## 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/connect-bybit.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.