Skip to main content
The Logs page is the request-level view of OpenRouter’s observability suite. Where Activity aggregates usage into charts, Logs shows you each generation as it happened: which model and provider served it, how long it took, what it cost, and, if you have enabled Input & Output Logging, the exact prompt and completion.
The Logs page showing the Generations tab with a table of recent generations

​
Tabs

The Logs page is split into tabs by the kind of record you want to inspect. Organization accounts also see an Org Member column so you can attribute generations to the member whose API key made the request.

​
Filtering

Use the filter bar above the table to narrow the list by user, model, provider, status, region, API key, or modality, depending on the tab. You can also filter by a specific generation ID to jump straight to one record. Filters are stored in the URL, so you can bookmark or share a filtered view. A request histogram above the table shows volume over the selected date range so you can spot spikes before drilling into individual rows.

​
Generation details

Click any row to open the generation detail sheet.
The generation detail sheet showing latency, cost, token counts, request metadata, and the provider response waterfall
It contains:
  • Overview: model, provider, cost, token counts, finish reason, streaming flag, provider latency and throughput, data region, and any fallbacks that occurred.
  • Provider Responses: a waterfall of each upstream attempt in order, with latency, moderation time, and overhead, so you can see why a request landed where it did.
  • Usage: a cost breakdown including cache read discounts, BYOK upstream cost, web search, web fetch, and file processing charges.
  • Prompt and Completion: the full request and response content when Input & Output Logging is enabled.
  • Raw JSON: the underlying generation record.
From the detail sheet you can also open the generation in the Chatroom or replay it in the Playground with a different model or configuration.

​
Stored prompts and completions

By default OpenRouter stores only metadata about each generation. To keep the prompt and completion text as well, enable Input & Output Logging under Settings > Observability. Only generations made after you enable it will have stored content.

​
API access

The same data is available programmatically. Both endpoints take the generation ID returned in the id field of a completion response.
  • Broadcast: send traces for every generation to your own observability platform.
  • Activity Export: download aggregated usage as CSV or PDF.