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

# AI usage tracking

> Monitor token consumption, cost, and adoption across every AI tool your team uses — OpenAI, Anthropic, Copilot, Cursor — with per-employee attribution.

AI usage tracking gives you a single view of what your organization spends on AI tools — across OpenAI, Anthropic, GitHub Copilot, Cursor, Google Gemini, Perplexity, and RouteShift. Layer pulls usage data directly from each provider's admin API and rolls it up by person, department, and provider so you can spot waste, justify renewals, and forecast budgets.

<Note>
  AI usage tracking is available on the **Scale** plan. See [Plans and billing](/layer/billing) for details.
</Note>

## Supported providers

| Provider           | Source    | Data collected                                              |
| ------------------ | --------- | ----------------------------------------------------------- |
| **OpenAI**         | Admin API | Tokens (input/output), cost per model, per-user attribution |
| **Anthropic**      | Admin API | Tokens (input/output), cost per model, per-user attribution |
| **GitHub Copilot** | Admin API | Seat assignment and usage                                   |
| **Cursor**         | Admin API | Token usage and cost per user                               |
| **Google Gemini**  | Admin API | Token usage and cost per user                               |
| **Perplexity**     | Admin API | Token usage and cost per user                               |
| **RouteShift**     | Admin API | Token usage and cost per user                               |

Layer syncs usage data automatically once you connect a provider integration. Each record is keyed by organization, user, tool, source, month, and model — so you never lose granularity.

## View AI spend

Open **AI Usage** in the Layer sidebar (between **Hardware** and **Renewals**) for the dedicated AI cost view. The page shows:

* **Per-person spend** — every user ranked by total monthly cost, with a breakdown by tool and model.
* **Department ROI** — total spend, active users, licensed seats, adoption rate, and cost per active user for each department.
* **Provider ROI** — the same metrics grouped by AI provider instead of department.
* **Three-month trend** — month-over-month cost and active-user changes so you can see whether spend is growing or stabilizing.

The provider ROI and per-person breakdowns also surface inside the **Apps** page so you can see AI spend in context with the rest of your SaaS portfolio.

## RouteShift integration

[RouteShift](https://routeshift.io) is the LLM proxy gateway behind Layer's AI cost tracking. When you mint a RouteShift API key per identity, every prompt, completion, and tool call is attributed to the employee who made it — so per-employee spend rolls up cleanly even across BYOK and credit-funded usage.

From the **AI Usage** page, use **Open RouteShift** to jump into the RouteShift dashboard for:

* Smart routing and savings — RouteShift picks the cheapest provider that meets your latency and quality bar.
* Live analytics — cache hit rate, p95 latency, error rate, and savings reporting on daily, weekly, or 24-hour windows.
* Per-employee key management and billing.

### RouteShift plans

RouteShift is sold separately from Layer and bills directly through Stripe. Each plan combines a fixed monthly base with a metered per-request overage line item, so you only pay for usage that exceeds the included allowance.

| Plan       | Base price | Includes                     | Overage                       |
| ---------- | ---------- | ---------------------------- | ----------------------------- |
| Starter    | \$9 / mo   | First 1,000 routed requests  | \$0.01 per additional request |
| Growth     | \$29 / mo  | First 10,000 routed requests | Metered per request           |
| Enterprise | \$99 / mo  | Higher routing volume + SLA  | Metered per request           |

Sign up at [routeshift.io](https://routeshift.io). Promotion codes (including `ANNUAL10` for annual billing and `FOUNDER` if eligible) work in checkout — see [Plans and billing](/layer/billing#promotion-codes) for the catalog.

<Note>
  Per-employee spend roll-up directly inside Layer is on the roadmap. Until then, manage keys, analytics, and billing in the RouteShift dashboard via the **Open RouteShift** link on the **AI Usage** page.
</Note>

## How costs are calculated

Layer stores costs in **microcents** (1/10,000th of a cent) to avoid rounding errors across high-volume token usage. When you see dollar amounts in the dashboard, they've been converted from microcents.

Each provider adapter maps the provider's native usage format to a standard record:

* **Input and output tokens** are tracked separately.
* **Model name** is preserved so you can compare cost across models (e.g. GPT-4o vs. GPT-4o-mini).
* **Usage month** groups records into calendar months (UTC).

## Adoption metrics

Layer calculates two key adoption metrics for every department and provider:

* **Adoption rate** — the percentage of licensed seats that are actively using the tool. A low adoption rate may indicate unused seats you can reclaim.
* **Cost per active user** — total monthly spend divided by the number of users who actually generated usage. Use this to benchmark whether a tool delivers value relative to its cost.

## Seat detection

Layer identifies unique seats by extracting provider-specific email addresses or user IDs from usage metadata. For example, a Cursor user is identified by their `cursor_user_email`, while an OpenAI user is identified by their `openai_user_id`. This means Layer can count licensed seats even when users have different identifiers across providers.

<Tip>
  Connect your identity provider (Google Workspace, Microsoft 365, or Okta) first. Layer uses identity data to map AI usage records to employees and departments automatically.
</Tip>