> For the complete documentation index, see [llms.txt](https://docs.strongdm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongdm.com/references/billing-information.md).

# Billing Information

Billing information for your organization may be viewed in the Admin UI on the **Settings** > **Account** page if you have the Administrator permission level. The billing section provides information about licenses and used/billable licenses.

Licenses are the number of StrongDM users that your organization has paid for. Used/billable licenses are the StrongDM users and service accounts that are active or inactive, and are not suspended or deleted as of the date and time of the last update.

These metrics can provide insight into the number of contracted licenses that your organization has paid for versus the number of licenses that are actually being used. If your organization currently has more licenses used than are contracted, the number of used/billable licenses is shown. For example, if 100 licenses are paid for and 118 licenses are being used, the **Used/Billable Licenses** value is `118 (18 more than licensed)`.

If there is a significant or persistent overage of licenses used, this overage may require an expansion of your organization's contract.


---

# 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.strongdm.com/references/billing-information.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.