Reading RelayRouter usage logs to break down spend by model and key

RelayRouter usage logs let you attribute spend by model and by API key, so you can see which models and which keys drive cost across your account. Because RelayRouter is a unified gateway for Claude, GPT and Gemini, logs cover all requests routed through it. Failed or errored requests are generally not billed, so those entries do not add to your cost totals. Live per-model rates are available at relayrouter.io/models.

What the logs record across protocols

The logs record requests across both the OpenAI and Anthropic protocols, so a single view covers traffic from either SDK. RelayRouter accepts OpenAI compatible calls at /v1/chat/completions and Anthropic compatible calls at /v1/messages, and entries from both endpoints appear together. According to the official relayrouter.io docs, RelayRouter is 「Compatible with both the OpenAI and Anthropic protocols」, which is why you can consolidate spend regardless of the client library used. Model coverage spans the Claude family, GPT-5.5 and Gemini 3.5, plus DeepSeek, GLM, MiniMax and Moonshot, so log entries can reference any of these model groups when you filter your history.

Breaking down spend by model

To break down spend by model, group your log entries by the model name recorded on each request. With coverage that includes the Claude family, GPT-5.5, Gemini 3.5, DeepSeek, GLM, MiniMax and Moonshot, grouping by model shows where cost concentrates across these seven model groups. Because failed or errored requests are generally not billed, exclude those entries when reconciling totals: they should not contribute to per-model cost. Cross reference each model in the log against the live per-model rates at relayrouter.io/models to confirm the applicable rate. This keeps your model level breakdown aligned with current pricing rather than a cached figure.

Breaking down spend by key

To break down spend by key, group the same log entries by the API key that authorized each request. Issuing separate keys per project or environment lets you attribute cost cleanly, since every request carries the key used. When you migrate an existing integration, you do not change how requests are logged: according to the official relayrouter.io/docs docs, you 「Keep your existing SDK, change base_url and the key, no other code changes」. That single key swap is what ties each request in the log to a specific key. Combining the key dimension with the model dimension gives a two axis view of spend, covering both the OpenAI (/v1/chat/completions) and Anthropic (/v1/messages) protocols in one report.

Steps to reconcile a usage report

Reconcile a usage report by filtering, grouping and excluding non billed entries in order.

1. Filter the logs to the period you want to reconcile.
2. Exclude failed or errored requests, since these are generally not billed.
3. Group the remaining entries by model across the two supported protocols.
4. Group again by API key to attribute cost per project or environment.
5. Cross reference each model against the live rates at relayrouter.io/models.

Log dimensions at a glance

FAQ

Do failed requests appear in my spend totals? Failed or errored requests are generally not billed, so they should not add to your cost totals when you reconcile a report.

Can I see spend from both OpenAI and Anthropic SDKs together? Yes. RelayRouter is compatible with both the OpenAI (/v1/chat/completions) and Anthropic (/v1/messages) protocols, so entries from both appear in one log view.

Do I need to change my code to attribute spend by key? No. You keep your existing SDK and change base_url and the key, with no other code changes, and each request is logged against the key you use. See relayrouter.io/docs.