Monitor and debug

Correlation headers

Send either or both headers with a model request:

X-Request-Id: req_checkout_summary_018
X-Trace-Id: trace_checkout_2026_07_24

Router echoes both and generates either one when it is missing, so the response always carries values you can log. Recording them alongside your own application logs is what makes a timeout, broken stream, or failed fallback findable afterwards.

Usage dashboard

Dashboard shows spend, tokens, request count, average cost per request, and routing cost delta over the range you select. Group by splits those totals across Gateway key, provider, model, or service tier.

Usage is recorded asynchronously, so a request takes a short time to appear.

Request logs

Logs lists each request's model, provider, status, tokens, cost, and latency. Opening one shows its IDs, API key, token breakdown, metadata, which service tier handled it, and the fallback candidates Router tried.

Logs record request metadata, cost, and usage. Prompt and response content is stored for 1 year by default, with opt-out in settings.

Trace a failure

1. Take the x-trace-id from the failed response, or the request ID you sent.
2. Find the request in Logs and check which candidates ran and how each ended.
3. Map the status code to a cause in Errors and limits.

When a request never reaches Logs at all, it failed before Router recorded usage — almost always authentication, so verify the client is sending your Router key against https://router-api.ramp.com/v1.