Skip to main content
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.
AI usage tracking is available on the Scale plan. See Plans and billing for details.

​
Supported providers

ProviderSourceData collected
OpenAIAdmin APITokens (input/output), cost per model, per-user attribution
AnthropicAdmin APITokens (input/output), cost per model, per-user attribution
GitHub CopilotAdmin APISeat assignment and usage
CursorAdmin APIToken usage and cost per user
Google GeminiAdmin APIToken usage and cost per user
PerplexityAdmin APIToken usage and cost per user
RouteShiftAdmin APIToken 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

Go to Apps in your Layer dashboard and look for the AI usage section. 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.

​
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.
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.