Request logs

Open User → Request Logs. This view lists real inference calls through the Proxy: timestamps, keys, users, models, route groups, status, and more — useful for troubleshooting and reconciliation.

Request Logs helps filter calls by time range, status, model, provider, protocol, and user. Emails and sensitive identifiers are pixelated in this screenshot.

Prerequisite

Traffic must hit the Proxy. Playground checks do not appear here; for production-like rows use a real key against the Proxy or Simulator.

What to do in Admin

1. Open Request Logs.
2. Narrow results with time range, status, model, user email, API key, vendor, route group, protocol, and other filters available on the page.
3. Expand a row to inspect billing-audit snippets, request bodies, upstream bodies, and raw usage JSON (copy when provided).
4. When reading money and timestamps, align with your system timezone and billing currency settings in Admin.

Billing display

Expanded panels may include charge-related JSON summaries; for exact formulas or finance reconciliation, follow your internal policy plus upstream docs linked from the GitHub technical reference.

Next

• Audit logs — budget and account-side changes
• Simulator — browser-based calls to the Proxy with a real key