> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-core/license-usage.md).

# License Usage

### Subscription

Provides a consolidated view of the license subscription, its validity, and consumption across different IZ modules. It is intended to give administrators quick insight into license health, usage trends, and entitlement limits.

1. Navigate to **`Global Settings`** → **`License`** -> **`Subscription`**

Each module table typically contains:

**`Module Name`** – The specific capability or resource governed by the license 

**`Allowed`** – The maximum quota permitted under the subscription 

**`Actual`** – The current consumption against that quota

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FryhRBLKmZTeQmZYHVrGH%2Flicense-subscription.png?alt=media&amp;token=de46bb96-413b-4052-9f66-eebe21b9f042" alt=""><figcaption></figcaption></figure>

### Developer Keys

Provides a centralized view of all IDE developer keys associated with a subscription. It is intended for administrators to manage, monitor, and govern developer key usage independently.

1. Maintain an inventory of issued IDE developer keys
2. Monitor usage against key-specific allocations
3. Identify keys that are fully utilized, underutilized, or unassigned

There are 2 actions associated for each developer keys:

1. **`Assign User`** - Assign a user for the Developer key for reference
2. **`View Scanned Projects`** - View the list of projects scanned against the developer key

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FEdO6eNA6lw5jy0SJXSOR%2Fide-developer-keys.png?alt=media&amp;token=90f67f8e-aaef-46fa-bf88-afd17c75fae1" alt=""><figcaption></figcaption></figure>

### See Also

* [Enabling MCP Server](/product-guides/integral-zone/iz-suite/iz-core/mcp-server.md)
* [Configuring STDIO MCP Server](/product-guides/integral-zone/iz-suite/iz-core/mcp-server/stdio-mcp-server-configuration.md)
* [Configuring HTTP MCP Server](/product-guides/integral-zone/iz-suite/iz-core/mcp-server/http-mcp-server-configuration.md)
* [MCP Tools](/product-guides/integral-zone/iz-suite/iz-core/mcp-server/mcp-tools.md)


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-core/license-usage.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.