OpenRouter launches upgraded analytics API with runaway agent monitoring

OpenRouter announced a major upgrade to the API that powers its activity dashboard, adding the ability to view and query usage data at the granularity of individual agents, models, and requests. The new interface exposes metrics for spend, tokens, cache hit rate, latency, and blended cost per token, with drill-down from any chart directly to the underlying details.

Runaway agent monitoring by trend, not volume

The standout addition is a “Runaway agent monitoring” mechanism. Instead of sorting consumption by size, the system ranks by movement. A dedicated panel tracks what rises and falls over time across models, users, API keys, and applications, making it easy to spot an out-of-control agent or a newly accelerating model within an organization. “When we ran the tool internally, it identified a preview model that burned about $6,200 per month at 25× the normal blended cost, and 98% of the spend was attributed to a single source,” the company said.

Explore tool for custom views

The Explore module lets users build independent views: select a metric—spend, tokens, cache hit rate, or latency—at percentile resolution (P50/P90/P99), group by dimensions such as model, application, user, or any custom classifier, and choose an aggregation method. Views can be saved for personal use or shared across the organization, turning analysis into a collaborative layer rather than a solitary task.

API for coding agents to audit costs

The new API is designed for coding agents to consume directly: provide the agent with a management key and the skill openrouter-analytics, and it runs an automatic cost audit. This shifts expense monitoring from a passive dashboard to an active process that runs as part of the development pipeline, without a human intermediary pulling reports manually.

Missing details

The announcement does not specify when the API will be open to all users, whether there are rate limits or separate pricing for analytical access, or the exact permissions required from a management developer. Technical parameters, such as the time window used for trend calculations in Runaway monitoring or the historical percentile resolution, were also omitted. OpenRouter says more information will follow, but for now the release is a capability announcement rather than full documentation.