4.4 Usage Statistics

Overview

The usage statistics feature records and analyzes API request data, helping you:

• Understand API usage patterns
• Estimate cost expenditure
• Analyze usage patterns
• Troubleshoot issues

Starting from v3.13.0, usage data comes from two sources:

• Codex sessions: Switched to precise parsing based on JSONL session logs, replacing the previous estimation; model names are normalized for consistent pricing lookup
• Gemini sessions: Synced precisely from Gemini CLI session logs
• Claude sessions: Also supports direct usage import from session logs
• The usage panel supports per-app filtering (Claude / Codex / Gemini) so data from different apps does not mix

Prerequisites

Depending on which data source you use, the prerequisites differ:

Proxy request log (covers all apps and all proxy requests):

1. Proxy service started
2. App takeover enabled
3. Log recording enabled

CLI session log (new in v3.13, no proxy required):

1. The corresponding app (Claude / Codex / Gemini) is enabled in CC Switch
2. The corresponding CLI has session history files
3. CC Switch periodically scans session directories and imports usage data

Open Usage Statistics

Settings > Usage Tab

Statistics Overview

Summary Cards

Key metrics displayed at the top of the page:

Starting from v3.15.0, the top of the Usage page uses a filter-driven Hero card. When you change the date range, app, provider, or model filters, the Hero's real total tokens, cache hit rate, request count, and cost update together and stay aligned with the logs and stats below.

Note: v3.15.0 normalizes cache reads, cache creation, and OpenAI-style cache reporting. Historical token and cost numbers may differ from older estimates; the current numbers follow the normalized rules.

Time Range

Select the time range for statistics:

Image: image-20260108011730105

Trend Charts

Request Trend

Line chart showing the trend of request counts:

• X-axis: Time
• Y-axis: Request count
• Viewable by hour/day
• Supports zoom and drag

Token Trend

Shows token usage trends:

• Input Tokens (blue) - Prompt content sent by the user
• Output Tokens (green) - Response content generated by AI
• Cache Creation Tokens (orange) - Tokens consumed when first creating cache
• Cache Hit Tokens (purple) - Tokens saved by reusing cache
• Cost (red dashed line, right Y-axis) - Estimated cost

Cache Token explanation: Anthropic API supports Prompt Caching. Creating cache incurs a higher fee (typically 1.25x input price), but subsequent cache hits only charge 0.1x, significantly reducing costs for repeated requests.

Time Granularity

• Today: Displayed by hour (24 data points)
• 7 Days/30 Days: Displayed by day

Image: image-20260108011742847

Detailed Data

Three data tabs at the bottom of the page:

Request Logs

Detailed record of each request:

Timing Information

The timing info column displays multiple badges:

View Details

Click a request row to view detailed information:

• Complete request parameters
• Response content summary
• Error messages (if failed)

Filter Logs

Supports filtering by the following criteria:

Action buttons:

• Search: Apply filter criteria
• Reset: Restore defaults (past 24 hours)
• Refresh: Reload data

Image: image-20260108011859974

Provider Statistics

Statistics grouped by provider:

Image: image-20260108011907928

Model Statistics

Statistics grouped by model:

Image: image-20260108011915381

Pricing Configuration

Open Pricing Configuration

Settings > Advanced > Pricing Configuration

Configure Model Prices

Set prices for each model (per million tokens):

Model ID Normalization Rules

Before matching pricing, CC Switch normalizes the requested model ID:

• Remove everything before the last / and convert to lowercase
• Remove everything after : and trim a trailing [1m]
• Replace @ with -
• Remove common wrapper prefixes, version suffixes, and date suffixes (-YYYY-MM-DD, -YYYYMMDD)
• Some model families can match a short ID to a versioned pricing entry

When adding pricing entries, enter the normalized Model ID rather than the full raw model name from the request.

Operations

• Add: Click the "Add" button to add model pricing
• Edit: Click the edit icon at the end of the row to modify
• Delete: Click the delete icon at the end of the row to remove

Image: image-20260108011933565

Preset Prices

CC Switch includes preset official prices for common models (per million tokens). v3.13.0 corrects CNY → USD pricing for several models and adds previously missing model definitions; it also fixes MiniMax plan quota math and the 0% → 100% usage progress display, making cost estimates and plan progress more accurate.

Claude Series (USD):

OpenAI Series / Codex (USD):

Note: Codex presets include low/medium/high variants with prices identical to the base model.

Gemini Series (USD):

Chinese Provider Models:

Note: Currency follows each provider's official pricing page. StepFun is currently listed in USD.

DeepSeek compatibility: Legacy model IDs deepseek-chat / deepseek-reasoner now alias to deepseek-v4-flash (non-thinking / thinking modes) and are billed at v4-flash rates.

Custom Prices

If using proxy services, prices may differ:

1. Click the "Edit" button
2. Modify prices
3. Save

FAQ

Statistics Data Is Empty

Check:

• Is the proxy service running
• Is app takeover enabled
• Is log recording enabled
• Have requests been going through the proxy

Cost Estimates Are Inaccurate

Possible causes:

• Pricing configuration doesn't match actual prices
• Using a proxy service with special pricing

Solutions:

• Update pricing configuration
• Refer to the provider's actual invoices

Token Count Differs from Provider

CC Switch uses its own method to estimate token counts, which may slightly differ from the provider's calculation. Refer to the provider's invoice for authoritative numbers.