> 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-analyzer/license-usage.md).

# License Usage

IZ Analyzer license details and developer keys usage are available at [https://license-usage.integralzone.com](https://license-usage.integralzone.com/). Sign in to the application using the license key issued by Integral Zone.

### Developer Keys

Provides a centralized view of all IDE developer keys associated with a subscription. It is intended for administrators to check developer key usage independently.

1. Maintain an inventory of issued IDE developer keys
2. Identify keys that are fully utilized, underutilized

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FsqSi3TzGdPN5c5MjHhk2%2Fdeveloper-tokens.png?alt=media&amp;token=cf5381e3-ad0b-43aa-b541-d11cdfabb723" alt=""><figcaption></figcaption></figure>

### License Details

Provides a consolidated view of the license subscription, its validity and entitlement limits.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fn1MvRd52t27BBId8KiYR%2Flicense-details.png?alt=media&amp;token=4f949378-bd08-4808-92d3-24d78bcfe39f" alt=""><figcaption></figcaption></figure>

### See Also

* [Code Analysis In Anypoint Studio](/product-guides/integral-zone/iz-analyzer/source-code-analysis/code-analysis-in-studio.md)

***

[SonarQube™](https://www.sonarqube.org) is a trademark belonging to SonarSource SA. For further information, please visit [www.sonarqube.org](https://www.sonarqube.org).


---

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