> ## Documentation Index
> Fetch the complete documentation index at: https://unkey.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Unkey is two separate products. Compute builds, deploys, and runs apps behind a gateway. API Management issues API keys, enforces rate limits, manages identities and permissions, and reports usage. Say which product a page belongs to; a reader can use either without the other.
> Every Unkey API endpoint is an HTTP POST to https://api.unkey.com/v2/{service}.{procedure} with a root key in the Authorization: Bearer header. Root keys are workspace scoped.
> Error codes have the form err:{system}:{category}:{specific} and each has a page at /errors/{system}/{category}/{specific}.
> The word environment means production or preview in Compute. Rate limiting has four meanings on this site; the glossary lists them.

# Usage

> Check what your workspace has used this month before the invoice arrives.

Usage covers one calendar month (UTC), with one total per product: API for every workspace, Compute once you have a Compute plan.

## API management

Usage has two parts, **Key verifications** and **standalone rate limit operations**, metered against your monthly operations quota. Only successful calls count: invalid, expired, or over-limit requests aren't billed. These two are the billable operations that [Limits](/docs/platform/billing/limits) caps and that a paid API tier prices.

<Frame>
  <img src="https://mintcdn.com/unkey/TjbnJStfcJRkiuek/images/dashboard/platform--billing-usage--api.png?fit=max&auto=format&n=TjbnJStfcJRkiuek&q=85&s=537db605606b0ac44f4dd76e98348e96" alt="Usage page showing Compute cost per app and, below it, API management requests this period split into key verifications and rate limit operations" width="2560" height="1600" data-path="images/dashboard/platform--billing-usage--api.png" />
</Frame>

## Compute

Compute usage totals cost for the period, broken down by project, then <Tooltip tip="A Compute app: a deployable service inside a project. Not 'your application' in general.">app</Tooltip>, then <Tooltip tip="A production or preview environment of a Compute app, not the dashboard label on a key.">environment</Tooltip>. Each level shows four quantities and a cost.

<Frame>
  <img src="https://mintcdn.com/unkey/TjbnJStfcJRkiuek/images/dashboard/platform--billing-usage--compute.png?fit=max&auto=format&n=TjbnJStfcJRkiuek&q=85&s=c526331f8060bd24338b930e9812aa9e" alt="Usage page with a daily Compute cost chart and a project expanded to show spend by resource and cost per app" width="2560" height="1600" data-path="images/dashboard/platform--billing-usage--compute.png" />
</Frame>

| Quantity | Meaning |
| - | - |
| CPU (vCPU-hrs) | vCPU allocated to running instances, integrated over time. |
| Memory (GiB-hrs) | Memory allocated to running instances, integrated over time. |
| Egress (GiB) | Bytes sent out of the platform. |
| Storage (GiB-hrs) | Ephemeral disk allocated, integrated over time. |

If a project uses gateway key auth, it also carries **Verified keys**: those verifications bill to the project, not a keyspace.

Usage is what you consumed. [Limits](/docs/platform/billing/limits) are the ceilings. Costs here are the metered part of the bill. The plan fee and included credit are on [Plans](/docs/platform/billing/plans).