Skip to main content
This page defines the key concepts, metrics, and data practices for Tokenomics.

​
Key concepts in Tokenomics

  • Active user: A person who used a connected AI coding tool at least once during the selected period. Activity is independent of spend, so usage covered by a free allowance still counts. People with multiple accounts or providers are counted once.
  • Adoption: A metric category that tracks AI tool activity and the number of people actively using each connected provider.
  • Average cost per active user: Total cost divided by total active users for the selected providers, models, and period.
  • Cost: A metric category that tracks AI tool token usage and expenses by provider and model.
  • Provider: A connected AI coding tool integration. Tokenomics supports OpenAI Codex, Anthropic Claude Code, Cursor, GitHub Copilot, and Windsurf.
  • Model: The specific AI model associated with a usage or cost record, such as a Claude or Codex model. Model-level detail is available only for cost and token data. Adoption is tracked by provider, not by model.
  • Tokens: Units of text consumed or generated by an AI model. Tokenomics reports total tokens and cost by provider and model.
  • Total cost: The total usage cost in USD for the selected providers, models, and period.
  • Data as of: The timestamp of the most recent data included in the current results. Because data refreshes daily, this typically reflects activity through the end of the previous day.
  • Team roll-up: Metrics aggregated for a manager and everyone in their reporting chain, based on the imported organization chart.
  • Workforce filters: Filters for directory attributes such as department, job family, and region or country. Available only to organizations with an imported organization chart.

​
About Tokenomics metrics

​
Eligibility and activity windows

A person counts as an active user on a given day if any connected provider account records activity that day. Activity and cost may be reported separately. Because providers use different data sources and schedules, a user may appear as active without showing cost, or show cost without appearing as active for the same day.

​
Cost calculation

Tokenomics uses each vendor’s reported or estimated costs and activity data. It doesn’t independently audit or recalculate vendor-reported spend or token counts. Cost sourcing varies by provider:
  • Codex: Credits are converted to USD using an organization-configured credit rate.
  • GitHub Copilot: Enterprise cost excludes usage covered by the organization’s included AI credits. Only usage beyond that allowance is billed. A $0 cost for Copilot may be displayed if the organization credit for all employees hasn’t been exhausted yet.
  • Windsurf: Cost combines an organization-configured seat price with prompt-credit usage beyond the plan’s included allowance.
All costs are normalized and displayed in USD.

​
Aggregation

Metrics can be viewed organization-wide or rolled up by manager and team using the imported organization chart. Metrics can be broken down by provider, or by model for cost and token data. Each result includes a Data as of timestamp showing the most recent data available for the selected window and filters.

​
Headless and service accounts

Tokenomics doesn’t identify or exclude headless, bot, or service accounts. It counts every user identity reported in a provider’s usage or activity data. Organizations can configure a list of work countries from their imported organization chart. Users in those countries are excluded from both cost and adoption data for data residency and compliance purposes.

​
Data refresh cadence for Tokenomics

Tokenomics data refreshes daily at 12:00 a.m. PDT. Each scheduled sync ingests the previous full day’s activity for every connected provider integration at the default 24-hour interval. A day’s data appears on the dashboard only after ingestion for that day is complete for the provider. Partial or in-progress ingestion isn’t shown. New integrations, hierarchy changes, and provider activity may not appear until the next refresh. Splunk Agent Observability doesn’t currently backfill data. If a provider publishes usage data after the daily refresh, it won’t be added retroactively to previous dates. The data becomes available after a subsequent refresh.

​
Who can view Tokenomics data

The following tables describe Tokenomics data visibility by role. For more information on Splunk Agent Observability roles, see Access control.