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

# Usage Dashboard

> Detailed visibility into usage, cost, tokens, and activity across tenants, teams, keys, models, and agents.

## Overview

The **Usage Dashboard** provides comprehensive visibility into how LLMGrid is being used across your tenant. It combines cost, request, token, and activity metrics with multiple breakdown views to support engineering, platform, and FinOps use cases.

All metrics respect the selected **tenant** and **time range**.

***

## Time Range & Export

### Select Time Range

Use the time range selector to filter all dashboard data to a specific period.

### Export Data

Select **Export Data** to download usage and cost metrics for reporting or offline analysis.

***

## Usage Views (Top Tabs)

The dashboard includes multiple high-level usage tabs to analyze consumption from different perspectives.

### Global Usage

Provides an aggregated view of all usage within the tenant.

**Best for:**

* Overall platform adoption
* Total spend and token consumption
* Executive-level reporting

***

### Organization Usage

Breaks down usage by organization.

**Use this view to:**

* Compare usage across business units or customers
* Attribute spend at the organization level
* Support chargeback or showback models

***

### Team Usage

Displays usage grouped by teams.

**Best for:**

* Monitoring team-level consumption
* Identifying high-usage teams
* Enforcing team budgets and policies

***

### Tag Usage

Analyzes usage using tags applied to requests or keys.

**Best for:**

* Project-level cost attribution
* Environment-based tracking (e.g., dev, staging, prod)
* FinOps and internal billing workflows

***

### User / Agent Activity

Shows activity by individual users and agents.

**Use this view to:**

* Track adoption by users
* Monitor agent-driven traffic
* Investigate anomalous behavior or spikes

***

## Metrics Tabs

Below the usage views, additional tabs provide operational breakdowns.

### Cost

Focuses on spend-related metrics and trends.

Includes:

* Total and daily spend
* Average cost per request
* Spend by model, key, and provider

***

### Model Activity

Displays usage metrics by model.

**Includes:**

* Request volume per model
* Token usage by model
* Cost contribution per model

Use this tab to optimize model selection and control spend.

***

### Key Activity

Shows usage and cost metrics grouped by virtual keys.

**Includes:**

* Requests per key
* Tokens consumed
* Spend attributed to each key

Useful for auditing integrations and identifying overactive keys.

***

### MCP Server Activity

Tracks activity associated with MCP servers.

**Includes:**

* Requests routed through each server
* Success and failure rates
* Token and cost metrics

Used to monitor server-backed or tool-augmented workflows.

***

## Summary Metrics

### Project Spend

Shows total spend for the selected period along with any configured budget limit.

***

### Usage Metrics

High-level KPIs for quick assessment:

* **Total Requests**
* **Successful Requests**
* **Failed Requests**
* **Total Tokens**
* **Average Cost per Request**

These metrics help assess reliability, efficiency, and scale at a glance.

***

## Visualizations

### Daily Spend

Bar chart showing spend per day.

**Use this chart to:**

* Identify usage spikes
* Correlate cost with releases or traffic changes
* Track day-over-day trends

***

### Top Virtual Keys

Displays API keys ranked by spend.

Supports:

* Table view
* Chart view

Best for attribution and key rotation decisions.

***

### Top Model Usage

Visualizes spend and usage by model name.

Use this to:

* Identify cost-driving models
* Compare performance and efficiency across models

***

### Spend by Provider

Breaks down usage across providers.

Includes:

* Total spend
* Successful requests
* Failed requests
* Total tokens

***

## Common Use Cases

* Monitor platform adoption and growth
* Attribute cost to teams, projects, or environments
* Optimize model and routing decisions
* Support budgeting and financial governance
* Investigate spikes, failures, or unexpected usage

***

## Best Practices

* Review the dashboard regularly to avoid cost surprises
* Combine **Tag Usage** with budgets for accurate cost allocation
* Monitor **Average Cost per Request** after model or prompt changes
* Audit **Key Activity** to secure and rotate unused keys
* Use **Model Activity** to balance quality and efficiency