> 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/others.md).

# 方案、用量與計費

- [試用與訂閱方案](https://docs.maiagent.ai/others/trial-and-plans.md): 瞭解試用版與各方案的差異及升級方式 — Credits 制下一份額度涵蓋所有 AI 功能。
- [Credits 計費制度](https://docs.maiagent.ai/others/credits.md): MaiAgent 平台的 Credits 點數計費制度、模型費率表與價格（定價）查詢 — 一份額度涵蓋所有 AI 功能。
- [成員 Credits 額度管理](https://docs.maiagent.ai/others/credits/member-credit-quota.md): 為每位成員設定個人 Credits 消費上限（額度）；成員可在 MaiGPT「用量與額度」查看自己的剩餘額度。
- [對話平台 Credits 額度管理](https://docs.maiagent.ai/others/credits/inbox-credit-quota.md): 為每個對話平台設定 Credits 消費上限，控管各對話平台（官網、LINE 等）的 AI 使用成本
- [三種額度怎麼算：情境範例與常見問題](https://docs.maiagent.ai/others/credits/credit-quota-scenarios.md): 成員額度、角色額度、對話平台額度三種額度怎麼算、怎麼分辨，以「業務部」實際數字一步步帶您看懂，並整理最常被問到的問題。
- [用量計算](https://docs.maiagent.ai/others/usage.md): Credits 制度下平台用量計算方式 — 一份額度同時涵蓋對話、語音、生圖、文件解析等所有 AI 功能。
- [用量統計](https://docs.maiagent.ai/others/usage-statistics.md): 組織設定「用量統計」頁的完整說明：誰可以使用與如何依角色限定只看授權 Agent、篩選條件、用量概覽與快取節省、各分頁（Agent、角色、成員、對話平台、聯絡人、語音助理、計費類別）的欄位定義、角色用量的計算方式、「未知」代表什麼，以及為什麼和額度頁的數字不同。


---

# 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/others.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.