> 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/trade-scoped-keys.md).

# Trade-scoped keys

TradeSurge only accepts keys that can trade but cannot move funds out. It checks this before accepting a key.

TradeSurge needs permission to place trades on your account. It never needs permission to move money out. A trade-scoped key gives exactly that: read and trade, with withdrawals and transfers turned off.

{% hint style="info" %}
**Early access.** Key registration opens with the alpha, for invited traders.
{% endhint %}

## Keys are checked before they are accepted

When you paste a key, the engine asks Bybit what the key can do. It refuses the key if it can withdraw funds or move them between sub-accounts. If Bybit's answer is unclear or the check fails, the key is refused. TradeSurge never accepts a key on trust.

## Why a read-only key is not enough

A read-only key can show your balance, but it cannot place orders. TradeSurge executes trades for you, so it needs trade permission. Withdrawal permission stays off.

## Rejection reasons

| Name                                     | What it means                                                                            |
| ---------------------------------------- | ---------------------------------------------------------------------------------------- |
| **This key can withdraw funds**          | Create a trade-only key with withdrawal and transfer turned off, then try again.         |
| **This key cannot place trades**         | Turn on contract and order (trade) permission, keep withdrawal off, then try again.      |
| **The venue rejected these credentials** | Check the key and secret are correct, active and not IP-restricted away from the engine. |
| **This exchange account is blocked**     | This exchange account cannot be used with TradeSurge. Contact support.                   |
| **This account is not yours**            | Only the account owner can register keys.                                                |
| **"Account not recognized"**             | Refresh the page. If it persists, re-create the account.                                 |
| **Too many attempts**                    | Wait a moment, then try again.                                                           |
| **The request was not valid**            | Re-enter the key and secret and try again.                                               |

## You grant it, you revoke it

You can delete the key in Bybit at any time. TradeSurge loses access the moment you do.

## 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>Security and key custody</strong></td><td>How keys are stored and who can decrypt them.</td><td><a href="/concepts-and-reference/security-and-custody.md">Security and key custody</a></td></tr><tr><td><strong>Connect Bybit</strong></td><td>Add an 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/platform/accounts/trade-scoped-keys.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.