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

# Claude

> ConfigView indexes Claude Enterprise usage, cost, workspaces, and member data to provide a complete view of your AI infrastructure.

## Overview

ConfigView integrates with Claude's Admin API to provide visibility into:

* **Token Usage**: Granular tracking of token consumption across models and workspaces.
* **Cost Analysis**: Service-level cost breakdowns in USD.
* **Workspace Governance**: Inventory of workspaces and their settings.
* **Access Management**: Organization-wide member list and workspace-specific membership.

## Setup Guide

ConfigView uses two separate keys for Claude: an **Admin API Key** for Console-side data (usage, cost, workspaces, members) and a **Compliance Access Key** for Claude.ai chat analytics. The chat key is only required if you want the per-user Chat Usage Analytics dataset.

### 1. Provision an Admin API Key (Console)

1. Log in to the [Claude Console](https://console.anthropic.com/) as an **Organization Admin**.
2. Navigate to **Settings > API Keys**.
3. Create a new key. Ensure it is an **Admin API Key** (starts with `sk-ant-admin...`).
4. Copy the key and store it securely.

### 2. Provision a Compliance Access Key (Claude.ai chat analytics)

The Claude.ai chat analytics endpoint is gated by a separate Compliance Access Key with the `read:analytics` scope. This is distinct from the Console Admin API Key above.

1. As the **Primary Owner** of your Claude.ai organization, enable Compliance API access in **Settings > Data and Privacy**.
2. Create a Compliance Access Key and grant it the `read:analytics` scope (this is the `analytics_api` capability, separate from the standard compliance scopes).
3. Copy the key and store it securely.

### 3. Configure Secrets

In ConfigView, add the following secrets:

* `CLAUDE_ADMIN_API_KEY`: The Console Admin API key from step 1.
* `CLAUDE_CHAT_ADMIN_API_KEY`: The Claude.ai Compliance Access Key from step 2 (only required for Chat Usage Analytics).

## Data Points Indexed

### Usage Data

ConfigView tracks the following metrics for each model and workspace:

* `input_tokens_uncached`
* `input_tokens_cache_read`
* `input_tokens_cache_creation`
* `output_tokens`

### Cost Data

* `cost_cents`: Total cost in USD cents for service usage.

### Workspaces

* `name`: Workspace display name.
* `created_at`: Date the workspace was created.
* `archived_at`: Date the workspace was archived (if applicable).

### Member Management

* **Organization Members**: Full list of users in the organization with their roles (`admin`, `developer`, `billing`, etc.).
* **Workspace Membership**: Mapping of users to specific workspaces and their workspace-specific roles.

### Chat Usage Analytics

ConfigView retrieves per-user analytics for the Claude.ai chat interface:

* **Engagement**: Total `conversations` and `messages_sent` per user.
* **Consumption**: Token breakdown (`input`, `output`, `cache_read`, `cache_write`) per user.
* **Cost**: Actual USD spend attributed to individual users.