Usage, logs & audit

After traffic starts flowing, three Workspace modules keep you oriented.

Usage

Path: Workspace → Usage

Use Usage for trends:

• Requests over time
• Token volume
• Spend in USD
• Breakdowns that help you spot expensive models or noisy keys

Pair Usage with Billing balance alerts so finance and engineering see the same picture.

Call Logs

Path: Workspace → Call Logs

Use Call Logs when a single request misbehaves:

• HTTP status and latency
• Which model / provider answered (critical with fallbacks)
• Time range and status filters
• Correlation with the X-Request-Id your client stored

Overview also shows a recent-logs table so you can jump into debugging without leaving the dashboard.

Audit Log

Path: Workspace → Audit Log

Audit captures security-sensitive and configuration actions — key changes, policy edits, member updates, and similar events. Use it for incident review.

Suggested debugging loop

1. Reproduce or capture the failing X-Request-Id.
2. Find the row in Call Logs.
3. Confirm auth, balance, rate limit, or upstream failure from status + error body.
4. If a fallback fired, decide whether the chain or the primary model needs a change in Routing.
5. Check Audit if the failure followed a config change.