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

# Track usage

> See what each key and team is consuming and what it costs

Usage and cost show what your traffic is actually consuming. It's the reporting side of
[usage limits](/gateway/budgets-and-limits): limits set the cap, usage shows where you stand against it.

## Where to see it

* The **Usage limits** page shows each limit's current usage against its threshold for the active window.
* A **key's detail** page shows requests, tokens, and estimated cost over time, broken down by model and provider.

<img width="700" style={{ borderRadius: "0.5rem" }} src="https://mintcdn.com/openlayer-docs/0DNdDuuycN4Yl8SH/images/gateway/api_key_usage.png?fit=max&auto=format&n=0DNdDuuycN4Yl8SH&q=85&s=8966b08f4963370a5cef7675c3908c9e" alt="A key's usage and cost over time" data-path="images/gateway/api_key_usage.png" />

## What's tracked

For every key, the gateway records each day (UTC):

* **Requests**: how many calls the key made.
* **Tokens**: input plus output.
* **Estimated cost**: in USD.
* **Routing**: which incoming model and provider the caller asked for, and which target model and provider served it.

## How cost is estimated

The gateway multiplies token counts by its cached per-model pricing. Treat it as a close estimate
for tracking and budgeting, not as a replacement for your provider's invoice.

## Go deeper

Usage answers "how much." For request-level detail, including inputs and outputs, latency, and the
trace of each call, see [Observability](/gateway/observability).
