AI usage tracking is available on the Scale plan. See Plans and billing for details.
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 |
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.
RouteShift integration
RouteShift 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 |
ANNUAL10 for annual billing and FOUNDER if eligible) work in checkout — see Plans and billing for the catalog.
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.
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 theircursor_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.