Skip to main content
Full request history for your project. Find failed requests, track latency, audit which models are being called.

​
What each entry shows

FieldExample
ModelThe model that handled the request
Status200, 401, 403, 400, 420, 500
LatencyTime from request to response
TimestampWhen the request was made

​
Three ways to use logs

Debug a failure — Filter by 4xx/5xx status codes. Check the request payload for malformed input or missing headers. Investigate latency — Sort by latency. If slow requests correlate with high volume, you may need to adjust your request patterns. Audit usage — See which models are called, how often, and from which API keys. Useful for cost tracking across teams.
Logs show individual requests. Usage Analytics shows the trends. Use both.