> 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/deveoper-and-payment-engine/manual/access_information.md).
# 查詢API接入信息
要訪問Cregis API，您需要使用項目API密鑰、網關服務器和項目編號信息。您可以在項目中查詢相應信息並提供給開發人員。
選擇“項目”模塊並點擊“API”進入API界面。點擊API密鑰的顯示按鈕以顯示API密鑰信息。點擊右側的“複製”按鈕，分別複製API密鑰、網關服務器和項目編號信息。
**注意：不要輕易將項目API密鑰洩露給他人，否則可能會導致資產損失。**
---
# 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/deveoper-and-payment-engine/manual/access_information.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.
