> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/2.-transaction-and-account/openapi.md).
# General Setting
## Language
You can switch your language below. Cregis supports three languages, which are English, traditional Chineses and simplified Chinese.
## Currency
You can switch the currency below. Cregis supports three kinds of currency, which are USD, CNY and HKD. The exchange rate displayed by Cregis fluctuates according to the market but only refreshes when the user logs in or switches team spaces."
## Appearance
You can switch the device theme in appearance. Cregis provides Light and Dark modes for users.
## MPC Network Setting
If you find your internet is too slow, you can switch your MPC networking below. Cregis provides three servers for users. You can view the internet speed of different servers and choose the best one.
You can also turn on the automatic selection function. When this function is on, Cregis will help you select the best network each time you log in.
## Message Notification
You can turn on your message notification below. If you have turned it on, a notification sound will play when you receive a notification.
---
# 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.cregis.com/2.-transaction-and-account/openapi.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.
