> For the complete documentation index, see [llms.txt](https://support.tiger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.tiger.com/english/connections/crypto-exchanges/upbit.md).
# Upbit
{% hint style="success" %}
Starting from version 7.2, the [Tiger.com](https://tiger.com/) terminal supports connecting to the Upbit exchange in view-only mode with access to real-time and historical trading data.
{% endhint %}
To set up the connection:
1. Go to the **File -> Connections -> Setup** section in the terminal.
2. Click the **+ New Connection** button and select **Upbit** from the list.
3. Click the **Connect to Upbit** button to activate the connection:
Upon successful setup, you will see a corresponding confirmation message and a green icon next to the exchange name in the connections list:
---
# 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://support.tiger.com/english/connections/crypto-exchanges/upbit.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.
