> For the complete documentation index, see [llms.txt](https://broker-docs.tiger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://broker-docs.tiger.com/english-2/frequently-asked-questions/what-is-the-difference-between-a-personal-exchange-account-and-the-tiger.com-broker-account.md).

# What is the difference between a personal exchange account and the Tiger.com Broker account?

Your personal account on Binance/Bybit and your Binance/Bybit account via Tiger.com Broker are separate accounts that do not depend on each other. Because of this, there are a few key differences to note:

* The **deposit** you hold directly on the exchange is not connected to the deposit within Tiger.com Broker. To trade through Tiger.com Broker, you need to fund your **broker wallet** specifically. [Learn more about deposit](https://broker-docs.tiger.com/english-2/financial-operations/deposit).
* The **verification status** on Binance and Bybit does not affect your verification level in the Tiger.com Broker system. [A separate verification process](https://broker-docs.tiger.com/english-2/getting-started/verification) is required to approve your **broker account**.
* To receive **cashback** on exchange fees paid, you must trade using **API keys created directly in Tiger.com Broker**. Learn[ more about API keys creation](https://broker-docs.tiger.com/english-2/creating-api-keys).

{% hint style="info" %}
When trading through Tiger.com Broker, you will be executing trades **directly on Binance/Bybit** with the same **liquidity, activity, and trading rules** as on the exchanges themselves. The API keys created in Tiger.com Broker are identical to those on the exchange.
{% endhint %}


---

# 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://broker-docs.tiger.com/english-2/frequently-asked-questions/what-is-the-difference-between-a-personal-exchange-account-and-the-tiger.com-broker-account.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.