Feature Request: Per-credential usage statistics tracking

[wade56754]

Feature Description

Add per-credential usage statistics tracking to help users understand load distribution across multiple OAuth accounts.

Problem Statement

When running CLIProxy with multiple Claude OAuth accounts (e.g., 4 accounts with round-robin strategy), there's currently no way to:

1. See how many requests each account has handled
2. Track token usage (input/output) per account
3. Monitor error rates per account
4. Identify if one account is being rate-limited more than others

The current logging only shows:

[2026-03-05 23:00:42] [88ef569e] [info] 200 | 3.878s | POST "/v1/chat/completions"

No indication of which credential was used for the request.

Proposed Solution

Option A: Enhanced Logging (Minimal)

Add credential identifier to request logs:

[2026-03-05 23:00:42] [88ef569e] [info] [claude:user@example.com] 200 | 3.878s | POST "/v1/chat/completions"

Option B: Statistics API Endpoint (Preferred)

Expose usage statistics via the Management API:

GET /v0/management/stats/credentials

{
  "credentials": [
    {
      "type": "claude",
      "identifier": "user1@example.com",
      "stats": {
        "total_requests": 1250,
        "successful_requests": 1180,
        "failed_requests": 70,
        "tokens": {
          "input": 2500000,
          "output": 1200000,
          "cache_read": 800000
        },
        "last_used": "2026-03-05T23:00:42+08:00",
        "error_breakdown": {
          "429": 45,
          "500": 15,
          "other": 10
        }
      }
    }
  ],
  "period": "since_startup"
}

Option C: Prometheus Metrics

Export metrics in Prometheus format for integration with existing monitoring stacks:

cliproxy_requests_total{credential="user1@example.com",status="200"} 1180
cliproxy_tokens_input_total{credential="user1@example.com"} 2500000

Use Cases

1. Load Balancing Verification: Confirm round-robin is distributing evenly
2. Cost Attribution: Track API costs per account
3. Health Monitoring: Identify accounts with high error rates
4. Capacity Planning: Understand which accounts are approaching rate limits

Environment

• CLIProxyAPI Version: 6.8.40
• Config: 4 Claude OAuth accounts with routing.strategy: "round-robin"
• usage-statistics-enabled: true is set but no visible effect

Related

The usage-statistics-enabled config option exists but its output is not accessible. This feature request may involve surfacing existing internal statistics.

---

Thank you for this excellent tool! This feature would greatly help with multi-account management and monitoring.