> For the complete documentation index, see [llms.txt](https://docs.maiagent.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maiagent.ai/org/developer.md).

# 開發者工具

開發者與系統整合人員用的後台工具：API Key 管理、API 呼叫紀錄、OAuth 應用程式，以及讓 Claude、Cursor 等外部 AI 工具操作平台的 MaiAgent MCP。

開發者或系統整合人員用程式串接 MaiAgent 時，會用到以下後台功能：

| 工具                                                             | 用途                                                                        |
| -------------------------------------------------------------- | ------------------------------------------------------------------------- |
| [API Key 管理](/org/developer/api-keys.md)                       | 管理員為成員代發、限制、停用與撤銷 API Key；成員也可以在帳號頁面自行建立金鑰                                |
| [API 呼叫紀錄](/org/developer/api-logs.md)                         | 查看所有透過 API 呼叫 MaiAgent 的紀錄，包含請求內容、回應結果與效能數據，用來排查串接問題                      |
| [OAuth 應用程式](/org/developer/oauth-applications.md)             | 讓 MCP 客戶端等外部應用以 OAuth 授權連線，成員不必把 API Key 貼進設定檔                            |
| [MaiAgent MCP](https://docs.maiagent.ai/tech/mcp/maiagent-mcp) | 讓 Claude、Cursor 等外部 AI 工具透過 MCP 直接操作 MaiAgent 平台，例如建立 Agent、管理知識庫（技術人員手冊） |

## 程式串接文件 <a href="#integration-docs" id="integration-docs"></a>

* [技術人員手冊](https://docs.maiagent.ai/tech)：API 快速上手、Web Chat 嵌入與 SDK、MCP、AI Gateway、身分整合
* [API 文件](https://docs.maiagent.ai/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://docs.maiagent.ai/org/developer.md?ask=<question>&goal=<user_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.