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

# Tokenomics

> Monitor AI tool cost and adoption across your organization with Tokenomics

Monitor AI tool cost and adoption across your organization with Tokenomics. This feature brings usage data from supported AI third-party providers into Splunk Agent Observability so you can understand cost, adoption, and the teams behind them.

You can use Tokenomics to:

* Monitor your AI cost and adoption in one place, aggregated across supported AI providers.
* Track active users and usage patterns over time to see which tools teams actually use.
* Drill down from organization-level totals into providers, models, job families, managers, and individual users.

> [!NOTE]
>
> This documentation varies depending on your deployment type. Select the tab for your deployment type below.

**On-premises**

## Prerequisites

You must have the admin role to set up Tokenomics.

Before you begin, review the [Tokenomics key concepts and metrics](/concepts/tokenomics/tokenomics-concepts.md), including:

* [Data refresh cadence for Tokenomics](/concepts/tokenomics/tokenomics-concepts.md#data-refresh-cadence-for-tokenomics)
* [Who can view Tokenomics data](/concepts/tokenomics/tokenomics-concepts.md#who-can-view-tokenomics-data)

## Set up Tokenomics

**1. Navigate to the Tokenomics settings page**

Log into Splunk Agent Observability. From the main menu, select the **Tokenomics** tab. In the **Tokenomics** menu, select **Settings**.

**2. Connect your AI providers**

Use the **Provider integrations** section to add a provider integration and enter the credentials required by that provider. Splunk Agent Observability supports integrations for Claude Code, Codex, Cursor, GitHub Copilot, and Windsurf.

**3. Configure your fiscal calendar**

Use the **Fiscal configuration** section to configure the fiscal calendar used for reporting and future budget reviews. Review the configuration before saving to confirm that reporting periods align with your organization's fiscal calendar.

**4. Upload your organization hierarchy**

Use the **Organization directory** section to upload a CSV from Workday that maps each user's email address to their manager. You can also include organizational attributes, such as job family.

Splunk Agent Observability uses email addresses to match provider usage to people in your hierarchy.

The following organization chart CSV file headers are required:

| CSV file header | Description |
| - | - |
| `worker_id` | Immutable canonical user identifier from Workday |
| `username` | Workforce username |
| `work_email_address` | Primary work email; primary key for joining provider data |
| `assignment_status_group` | Assignment status group. Accepted values include `ACTIVE`, `LOA`, or `TERMINATED` |
| `regular_temp` | Worker type. Accepted values include REGULAR for full-time employees and TEMP for contingent employees |
| `manager_username` | Direct manager's username (not worker\_id) |
| `work_country_cd` | Work country code |
| `work_country_name` | Work country display name |

The following organization chart CSV file headers are optional:

> **Optional headers**
>
> | CSV file header | Description |
> | - | - |
> | `department_cd` | Department code |
> | `financial_department_name` | Financial department name |
> | `job_family_name` | Job family |
> | `region_cd` | Region code |
> | `alternate_mail` | Alternate email |
> | `person_full_name` | Full name displayed in the UI |
> | `sup1_manager_username` | Direct manager's username |
> | `sup2_manager_username` | Second-level manager's username (manager's manager) |
> | `sup3_manager_username` | Third-level manager's username |
> | `sup4_manager_username` | Fourth-level manager's username |
> | `sup5_manager_username` | Fifth-level manager's username |
> | `sup6_manager_username` | Sixth-level manager's username |
> | `sup7_manager_username` | Seventh-level manager's username |
> | `sup8_manager_username` | Eighth-level manager's username |
> | `sup9_manager_username` | Ninth-level manager's username |
> | `sup10_manager_username` | Tenth-level manager's username |
> | `sup11_manager_username` | Eleventh-level manager's username |

## Monitor AI tool adoption and cost

**1. Navigate to the Tokenomics tab**

Use the Splunk Agent Observability main menu to select the **Tokenomics** tab.

**2. Monitor overall AI cost and adoption in your organization**

Use the following panels for a high-level view of the AI cost and adoption across your organization:

* Cumulative AI Usage Cost
* Total AI Usage Cost
* Average Cost Per Active User
* Average Users
* Cost in USD (chart)

  ![Tokenomics high-level panels](https://mintcdn.com/agent-observability-docs/OKBJS6E-KybSRXNp/images/saas/tokenomics/tokenomics-cumulative-onprem.png?fit=max\&auto=format\&n=OKBJS6E-KybSRXNp\&q=85\&s=d1d3d6bdee7c441508424cb59e182281)

**3. Understand AI cost and adoption across teams**

Use the following panels to understand how cost is distributed across teams, providers, models, and roles:

* Cost heatmap
* Top 10 Cost
* Consumption by Job Family
* Cost in USD (table)

  ![Tokenomics drill down panels](https://mintcdn.com/agent-observability-docs/OKBJS6E-KybSRXNp/images/saas/tokenomics/tokenomics-drilldown-onprem.png?fit=max\&auto=format\&n=OKBJS6E-KybSRXNp\&q=85\&s=985c1d7da84bde215fb04f623bf799f2)

In the heatmap, manager totals include usage from people below that manager in the hierarchy.

**4. Investigate AI cost and usage by drilling down on provider, model, and more**

You can drill down to investigate AI cost and usage with the following methods:

1. Use the filters at the top of the page to filter data based on provider or leader.
2. In any panel, select a provider or model to focus the page on that scope.
3. In the heatmap, expand the hierarchy to investigate spend across a team or down to an individual contributor.
4. In the **Cost in USD** table, search for a user, model, or provider to show specific data.

**SaaS**

## Prerequisites

You must have the agent\_observability\_admin role to set up Tokenomics.

Before you begin, review the [Tokenomics key concepts and metrics](/concepts/tokenomics/tokenomics-concepts.md), including:

* [Data refresh cadence for Tokenomics](/concepts/tokenomics/tokenomics-concepts.md#data-refresh-cadence-for-tokenomics)
* [Who can view Tokenomics data](/concepts/tokenomics/tokenomics-concepts.md#who-can-view-tokenomics-data)

## Set up Tokenomics

**1. Navigate to the Tokenomics settings page**

Log into Splunk Observability Cloud. From the main menu, select **Agent Observability** > **Tokenomics** > **Settings**.

**2. Connect your AI providers**

Use the **Provider integrations** section to add a provider integration and enter the credentials required by that provider. Splunk Agent Observability supports integrations for Claude Code, Codex, Cursor, GitHub Copilot, and Windsurf.

**3. Configure your fiscal calendar**

Use the **Fiscal configuration** section to configure the fiscal calendar used for reporting and future budget reviews. Review the configuration before saving to confirm that reporting periods align with your organization's fiscal calendar.

**4. Upload your organization hierarchy**

Use the **Organization directory** section to upload a CSV from Workday that maps each user's email address to their manager. You can also include organizational attributes, such as job family.

Splunk Agent Observability uses email addresses to match provider usage to people in your hierarchy.

The following organization chart CSV file headers are required:

| CSV file header | Description |
| - | - |
| `worker_id` | Immutable canonical user identifier from Workday |
| `username` | Workforce username |
| `work_email_address` | Primary work email; primary key for joining provider data |
| `assignment_status_group` | Assignment status group. Accepted values include `ACTIVE`, `LOA`, or `TERMINATED` |
| `regular_temp` | Worker type. Accepted values include REGULAR for full-time employees and TEMP for contingent employees |
| `manager_username` | Direct manager's username (not worker\_id) |
| `work_country_cd` | Work country code |
| `work_country_name` | Work country display name |

The following organization chart CSV file headers are optional:

> **Optional headers**
>
> | CSV file header | Description |
> | - | - |
> | `department_cd` | Department code |
> | `financial_department_name` | Financial department name |
> | `job_family_name` | Job family |
> | `region_cd` | Region code |
> | `alternate_mail` | Alternate email |
> | `person_full_name` | Full name displayed in the UI |
> | `sup1_manager_username` | Direct manager's username |
> | `sup2_manager_username` | Second-level manager's username (manager's manager) |
> | `sup3_manager_username` | Third-level manager's username |
> | `sup4_manager_username` | Fourth-level manager's username |
> | `sup5_manager_username` | Fifth-level manager's username |
> | `sup6_manager_username` | Sixth-level manager's username |
> | `sup7_manager_username` | Seventh-level manager's username |
> | `sup8_manager_username` | Eighth-level manager's username |
> | `sup9_manager_username` | Ninth-level manager's username |
> | `sup10_manager_username` | Tenth-level manager's username |
> | `sup11_manager_username` | Eleventh-level manager's username |

## Monitor AI tool adoption and cost

**1. Navigate to the Tokenomics page**

Use the Splunk Observability Cloud main menu to select **Agent Observability** > **Tokenomics** > **Cost**.

**2. Monitor overall AI cost and adoption in your organization**

Use the following panels for a high-level view of the AI cost and adoption across your organization:

* Cumulative AI Usage Cost
* Total AI Usage Cost
* Average Cost Per Active User
* Average Users
* Cost in USD (chart)

**3. Understand AI cost and adoption across teams**

Use the following panels to understand how cost is distributed across teams, providers, models, and roles:

* Cost heatmap
* Top 10 Cost
* Consumption by Job Family
* Cost in USD (table)

In the heatmap, manager totals include usage from people below that manager in the hierarchy.

**4. Investigate AI cost and usage by drilling down on provider, model, and more**

You can drill down to investigate AI cost and usage with the following methods:

1. Use the filters at the top of the page to filter data based on provider or leader.
2. In any panel, select a provider or model to focus the page on that scope.
3. In the heatmap, expand the hierarchy to investigate spend across a team or down to an individual contributor.
4. In the **Cost in USD** table, search for a user, model, or provider to show specific data.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.