Skip to main content
Every tenant runs against a license that sets caps on hosts, gateways, and tasks. The Usage page lets administrators track consumption against those caps and explore LLM usage over time.
The Usage page, plan data, analytics, and the license banner are visible to administrators only.
A license is a signed token issued by 2501. Licenses can be contract or trial, and have a validity window (a license with no end date is shown as Perpetual).

​
Applying a license

1

Open Settings > License

In Command Center, go to Settings > License.
2

Paste the signed token

Paste the signed token (a JWT) issued by 2501 into the license field.
3

Apply License

Click Apply License. The new license becomes active immediately, and the previously active license is archived.
Only one license is active at a time. The License screen also shows a License history of every license you have applied; applying a new one archives the previous one.

​
How the task cap is enforced

The tasks cap is a tenant-wide lifetime count of every task ever created (ad-hoc and recurring combined). It is not reset per month, and it is enforced everywhere tasks are created: in Command Center (UI and API) and when the engine turns incoming gateway tickets into work. With no active license, or once the lifetime task cap is reached, task creation is rejected. See Tasks for how this surfaces during normal use.

​
The Usage page

The Usage page (administrators only) is where you watch consumption and dig into LLM activity.

​
Plan usage

The Plan-usage card shows a used-vs-cap bar for each entitlement (hosts, gateways, and tasks), plus the contract start and end dates and days remaining.

​
Usage banner

A tenant-wide banner appears across Command Center when hosts or tasks usage reaches 90% or more of its cap. The banner links straight to the Usage page.

​
Activity and LLM usage

The Usage page Activity section explores LLM usage over a date range, with a toggle between Cost and Tokens.
  • Tokens mode counts all token usage in the range: input, output, and cached tokens.
  • Cost mode stays anchored to tickets and pricing plans. Define pricing plans on your models so Cost mode can attribute spend.