> 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/supported-venues-and-firms.md).
# Supported venues and firms
TradeSurge opens first on Bybit demo, with MetaTrader 5 and MatchTrader coming next.
A venue is where your account actually lives. TradeSurge opens with one venue and has two more in progress. This page lists which venues are coming and which prop firms we track.
## Venues
| Name | What it means |
| ---------------- | ---------------------------------------------------------------------------------------------------------- |
| **Bybit (demo)** | Opening first to invited traders. You paste a trade-scoped key and secret, and stops rest on the exchange. |
| **MetaTrader 5** | Coming soon. Not connectable yet. |
| **MatchTrader** | Coming soon. Not connectable yet. |
cTrader, TradeLocker and DXtrade are on the list after launch.
## API-key-first
TradeSurge connects to any firm, broker or platform that gives out API-key access. We start with crypto firms on Bybit rails and add venues as they are certified.
## How a venue connection is used
TradeSurge will use your key to read balances and positions and to place and close trades. It never moves funds. We refuse any key that allows withdrawals or transfers. See [Trade-scoped keys](/platform/accounts/trade-scoped-keys.md).
## Every venue says what it can do
Venues differ. Some rest stops on the exchange, some do not. Each venue page states its capabilities plainly, so you know what protection you actually have before you connect.
## Prop firms we track
The Firm Catalogue holds 76 prop firms. Each record covers the firm's challenge rules, drawdown type, payout terms and whether it allows copy trading, bots and API access. Most records are marked low confidence while we re-verify them against each firm's own site.
{% hint style="info" %}
A firm's own rules always win. Check the firm's current terms before you buy a challenge or copy trades across accounts.
{% endhint %}
## A note on firm policies
Some firms forbid copy trading or automated trading. TradeSurge reads each firm's policy and refuses copy or autotrade on firms that forbid it. See [Copying across prop firms](/platform/terminal/copy-across-firms.md).
## 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/getting-started/supported-venues-and-firms.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.