OpenRouter expands observability with detailed logs, real-time broadcast, and activity export

The platform that aggregates access to dozens of models through a single API has launched a new visibility layer designed to give developers full control over what happens in production, without relying on guesswork or the partial logs that individual providers supply.

The logs page is now split into tabs by record type, and enterprise accounts see an additional column that attributes each generation to the organization member whose API key made the request. A filter bar narrows the list by user, model, provider, status, region, API key, or modality — depending on the tab — and can jump straight to a specific record via its generation ID. Filters persist in the URL so a filtered view can be saved or shared. Above the table, a histogram charts request volume across the selected date range, making it possible to spot spikes before drilling into individual rows.

Clicking a row opens a detail sheet with five sections. Overview shows the model, provider, cost, token count, finish reason, streaming flag, latency, provider throughput, data region, and any fallbacks that occurred. Provider Responses presents a waterfall of every upstream attempt in order, with latency, moderation time, and overhead cost, so teams can see why a request landed where it did. Usage breaks down the total cost including cache-read discounts, upstream BYOK charges, web-search fees, web retrieval, and file processing. Prompt and completion content appear only when Input and Output Logging are enabled, and Raw JSON exposes the underlying record.

By default OpenRouter stores only metadata for each generation. To retain prompt and completion content, users must enable Input and Output Logging under Settings > Observability; only generations created after the setting is turned on will include the stored content.

The same data is available programmatically through two API endpoints that accept the generation ID returned in the completion response's id field. Broadcast streams traces for every generation directly to an organization's internal observability platform, including a full matrix of supported fields for each destination. Activity Export downloads aggregated usage as CSV or PDF for reporting, billing, or audit purposes.