> 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/creating-api-keys/creating-api-keys-for-gate.io.md).
# Creating API keys for Gate.io
You need to create a read-only API key in your Gate exchange account and then bind this read-only API key to your Tiger.com Broker account:
1. Please make sure that the “Wallets” and “Account” toggles are enabled, and select “Read only” permission for both. All other toggles can be deactivated;
2. To create your API key, you may also be asked to set up a fund password. You can do this in your Gate profile settings: \
\
\
3. After creating your read-only API key with the appropriate permissions and toggles as described above, please try to bind it to your Tiger.com Broker account.
4. You may receive an error saying, “Generate a USDT deposit address on the Solana network in your exchange account” when attempting to bind your API key. If this happens, please go to the “Deposit” page of your Gate account, select “USDT” and the “Solana” network:\
\
\
\
\
\
The exchange will then generate the relevant deposit address. After that, please try to bind the API key to your Tiger.com Broker account once again.
---
# 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/creating-api-keys/creating-api-keys-for-gate.io.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.
