Request Logs and Usage
Inspect request status, latency, usage, and final cost in the console.
Use Request Logs to investigate individual calls and Usage to review trends across models and API keys.
Request logs
Filter calls by time, model, type, and status. A log can include the request ID, task ID, call mode, HTTP status, latency, time to first byte, usage meters, pricing rule, and final amount.
Request and response bodies are available only within the configured retention window. Binary and oversized content can be sanitized before storage.
Usage trends
Compare spend, token usage, and request counts over a selected period. Filter by API key or model to attribute cost to an environment or workload.
When contacting support, include the x-request-id value or the request ID shown in the log. See Errors, limits, and retries for common failure categories.
Help us improve this page
Found something unclear, outdated, or incorrect?
Last updated on