> 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/cregis-wallet-guide/zh-tw/accountmanagement/settings.md).
# 賬戶設定
## **語言**
您可以在下方切換語言。Cregis支持三種語言，分別是英語、繁體中文和簡體中文。
## **貨幣**
您可以在下方切換貨幣。Cregis支持三種貨幣，分別是美元（USD）、人民幣（CNY）和港幣（HKD）。Cregis顯示的匯率會隨市場波動，但僅在用戶登錄或切換團隊空間時刷新。
## **外觀**
您可以在外觀設置中切換設備主題。Cregis為用戶提供了淺色模式和深色模式。
## **MPC網絡**
如果您發現您的網絡速度過慢，您可以在下方切換MPC網絡。Cregis為用戶提供了三個服務器，您可以查看不同服務器的網絡速度並選擇最佳的服務器。
---
# 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/cregis-wallet-guide/zh-tw/accountmanagement/settings.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.
