> For the complete documentation index, see [llms.txt](https://docs.sealsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealsecurity.io/using-platform/usage-page.md).

# The Usage page

Where the tenant's consumption against its Seal subscription lives.

The Usage page shows what your tenant has consumed against your Seal subscription. It is the canonical place to check whether you are on track with your quotas, how usage has trended over time, and (for tenants with AI features enabled) how much of your AI token allotment has been spent.

The page lives under **Settings > Usage**. Four tabs split the data: **System** for the platform quotas, **AI agent** for AI-feature consumption, **Sealed packages** for the per-package pull history, and **Fix requests** for the sealed versions your tenant has requested. The AI agent tab is only shown to tenants that have enabled AI features.

## The System tab

The System tab covers the tenant's main subscription quotas. Three groups of content stack down the page: the subscription period, the quotas, and the trend charts.

<figure><img src="https://2109738374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FytkIsVkwVdKiLQ2CT6Sw%2Fuploads%2Fgit-blob-b85f52b6c037ceb2777875996bffda86fea84885%2Fusage-page-system-tab.png?alt=media" alt="The Usage page&#x27;s System tab showing subscription period, quota counters, and the trend chart."><figcaption><p>The Usage page System tab.</p></figcaption></figure>

### Subscription period

At the top, a widget shows the current subscription window: start date, end date, and where today falls within it. Use this to see how much of the period remains and to put the rest of the page's numbers in context.

### Quotas

Below the period widget, the page shows the count of each subscribed resource used so far versus what your subscription includes. Two quotas in scope:

* **Packages.** The count of sealed packages pulled across all your builds during this subscription period, versus the package count your subscription covers. This is the headline quota for most tenants.
* **CVEs.** The count of vulnerabilities Seal has helped you remediate this period, versus the CVE count your subscription covers. Tenants whose subscription does not cap CVEs see this row hidden.

The numbers reflect what Seal observed up to the snapshot's timestamp; see "Refresh cadence" below.

### Trend charts

Below the quotas, a chart shows usage over the subscription period. A toggle at the top of the chart switches between **Packages** (sealed packages pulled month by month) and **CVEs** (vulnerabilities remediated month by month). The chart marks the subscription start and the current month so you can see whether usage is concentrated in a part of the period or spread evenly.

The chart is hidden when usage is too low to plot meaningfully. New tenants typically see this state for the first few weeks; the chart appears once enough pulls have happened.

## The AI agent tab

The AI agent tab covers the tenant's AI token consumption. AI tokens are a single tenant-wide quota that covers both the [Seal AI Agent](https://docs.sealsecurity.io/using-platform/seal-ai-agent.md) (chat usage) and the [Seal Engineer](https://docs.sealsecurity.io/using-platform/seal-engineer.md) (flow runs); the platform does not split the budget between them. A heavy week on the Engineer counts against the same pool as a heavy week on the Agent.

The tab shows a per-user breakdown of consumption. Each user has:

* A token-usage bar showing their consumption against any per-user limits your tenant has set.
* Aggregate statistics: messages sent, flow runs initiated, and similar counters.
* The user's role chip from the platform's user list.

Tenants without AI features enabled do not see this tab.

## The Sealed packages tab

The Sealed packages tab lists the sealed packages your builds have pulled, one row per origin version (the vulnerable version the sealed version replaces). Use it when you need to look up a specific package rather than rely on the rolled-up numbers on the System tab.

Each row has these columns:

* **Package name**, **Version**, and **Ecosystem**: the package and its origin version.
* **First pulled**: when your builds first pulled a sealed version of it.
* **Last pulled**: when your builds most recently pulled a sealed version of it. The table is sorted by this column, newest first, by default.

Use the **Search packages** box to filter by package name.

### Filtering by pulled date

Use the **Filter by pulled date** control to narrow the table to a date range:

1. Open the filter and select the checkbox next to **First pulled**, **Last pulled**, or both.
2. For each selected row, enter a start date, an end date, or both. Type the date in your locale's format, or pick it from the calendar. Either end can be left empty to leave that side of the range open. Both ends are inclusive.
3. Check the **Selected range** summary, then select **Apply**.

When both rows are selected, a package must match both ranges to be shown. Packages without a value for a filtered date are hidden. **Apply** stays disabled while a date is invalid or a start date is after its end date.

The applied filter shows on the control. Select the **X** on it to clear the filter. The filter is saved in the page URL, so you can bookmark or share a filtered view.

## The Fix requests tab

The Fix requests tab lists your tenant's requests for sealed versions, such as the ones you make with [Generate fix](https://docs.sealsecurity.io/discovering/generate-fix.md). Use it to see what your tenant has asked Seal to build and which requests are still being worked on.

Each row is one requested version, with these columns:

* **Package name** and **Version**: the exact version that was requested. This can be the origin version, a sealed version, or a private version. If your tenant requested several versions of the same package, each requested version has its own row with its own status.
* **Ecosystem**: the package's ecosystem.
* **Request time**: when the request was made. The table is sorted newest first by default.
* **Status**: **In preparation** while Seal is still building the sealed version, or **Done** once the request is complete.

Use the **Search packages** box to filter by package name, and the **Status** filter to show only requests that are In preparation or Done.

## Refresh cadence

The tabs refresh differently. The header on each tab shows the last-updated time:

* **System and Sealed packages tabs**: the snapshot updates **once a day**. The number you see may be a few hours behind your most recent CI activity.
* **AI agent tab**: **live**, recomputed on each visit. Refreshing the page after a flow run shows the new consumption.
* **Fix requests tab**: **live**, recomputed on each visit.

For periodic checks, this difference rarely matters. For audits or end-of-period reviews, account for the System tab's daily-snapshot lag when interpreting the most recent numbers.

## Who can see the page

Everyone in the tenant can see the Usage page.

## Related

* [The Dashboard](https://docs.sealsecurity.io/discovering/dashboard.md): the tenant-wide aggregate view of vulnerability posture. Different data from the Usage page (posture vs consumption).
* [Triggering Generate fix](https://docs.sealsecurity.io/discovering/generate-fix.md): how to request a sealed version, which then appears on the Fix requests tab.
* [The Seal AI Agent](https://docs.sealsecurity.io/using-platform/seal-ai-agent.md) and [The Seal Engineer](https://docs.sealsecurity.io/using-platform/seal-engineer.md): the two AI features whose token usage shows up on the AI agent tab.
