Metrics and usage

Two pages cover this. Usage is the aggregate view, charts and totals. Metrics is the raw log, one row per request.

​

Usage

Everything here is scoped to the current workspace and to a date range you pick. Requests over time, split by model. Cost over time, in euros. Token split across input, output, cached read and cache creation. Model breakdown, a table of every model you called with its requests, tokens and cost. Distribution, which share of the workspace each model accounts for. The budget panel sits here too, showing spend against the workspace cap for the current month. See Quotas. You can filter to a single API key, which is the practical way to answer what one application is costing you.

​

Export

Any range exports as CSV or JSON, one row per request, carrying the model, the key that made the call, tokens, cost, latency and whether it succeeded.

​

Metrics

The request log. Every call through the gateway lands here, successful or not, including the ones that were refused before reaching a provider. Rows page 30 at a time and can be searched.

​

Origin

Calls made from your own code show their public address. Calls from our own products show a label instead: From chat for anything the chat product issued, From the SDK for an SDK client, Internal for a call that never left our network.

​

Blocked requests

A blocked row tells you why in plain language: a plan limit, a workspace budget, a quota rule, a request too large, too many at once. Nothing is charged for a blocked request, but it is still logged, which is what lets you see a client hammering a limit.

​

Detail

Opening a row shows the full record, including the models used within that request and their individual costs. A single gateway call can involve more than one model when a mapping or a workflow routes it.

​

What is not here

Metrics record what a request was and what it cost. They do not record prompt or response content. Message bodies are never written to this log.