> For the complete documentation index, see [llms.txt](https://doc.threatreaper.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.threatreaper.ai/user-guide/license-and-plan-management.md).

# 📜 License & Plan Management

**Menu:** Settings > License & Plan.

This page shows how your organisation's per-module credit balance is allocated and used. What you see depends on your role:

* **Standard view:** for each module (AI-Discover, AI-Probe, AI-Firewall, AI-Align, AI-Analytics, AI-Guard, AI-MCP, AI-Agents, AI-Explain), you'll see **Credits Available**, **Total Credited**, **Total Consumed**, and **Last Credit Added**.
* **Administrator view:** an organisation-wide breakdown — total users, available credits, credits used this month, your plan tier, and which modules are licensed. Expanding a row shows per-module usage with a progress bar.

## 16.1 Errors you might see and how to fix them

| **Message**                                               | **What it means**                                  | **What to do**                                                                                |
| --------------------------------------------------------- | -------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| "Failed to fetch organizations data" (administrator view) | The license data couldn't be loaded                | Refresh the page; if it persists, contact support                                             |
| "Failed to fetch transactions"                            | Your credit transaction history couldn't be loaded | Refresh the page, or try again later                                                          |
| A module shows 0 credits available                        | The balance for that module is exhausted           | Ask your administrator to add credits, or see [17. Payments & Billing](#17-payments--billing) |

## 16.2 What success looks like

AI-DISCOVER Credits: 5,000 Total Credited: 10,000 Total Consumed: 5,000

AI-FIREWALL Credits: 42,500 Total Credited: 50,000 Total Consumed: 7,500

A transaction history shows every credit movement:

| **Date**   | **Type** | **Amount** | **Balance** | **Module**  |
| ---------- | -------- | ---------: | ----------: | ----------- |
| 2026-10-10 | Add      |     +5,000 |      42,500 | AI-Firewall |
| 2026-10-09 | Use      |       −250 |      37,500 | AI-Discover |


---

# 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://doc.threatreaper.ai/user-guide/license-and-plan-management.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.