multi-router.aidocs

Observability

Request Tracing

Request, session, correlation and customer ids, and the response headers that describe how a request was served.

Request tracing ties a request in Multi-Router to the caller's own systems. Every response carries the request's id, and callers can attach their own ids, for a conversation, a job or an end customer, which Traffic records, filters and searches. Response headers also report how the request was served, such as the provider and the number of attempts, so an application can log them with its own records.

Ids

An id is a value that names a request, or a group of requests, in Traffic. A request carries these ids:

IdSet bySent asUse
Request idMulti-RouterReturned in x-mr-request-idFinds one request in Traffic.
Session idThe callerx-mr-session-id request headerGroups the requests of one conversation or agent session.
Correlation idThe callerx-mr-correlation-id request header, returned in the responseMatches a request to an entry in the caller's own logs.
Customer idThe callerThe user field on Chat Completions, or metadata.user_id on MessagesAttributes usage to the caller's end customer or tenant.

Traffic records the first 200 characters of a session or correlation id and matches them exactly, and the response returns the correlation id in full. Claude Code sends its own session id, which Traffic records when no x-mr-session-id is sent. With Anonymous Metadata, the router leaves the session id and customer id empty. See Request Logging.

A request with session, correlation and customer idsbash
curl https://api.multi-router.ai/v1/chat/completions \
  -H "Authorization: Bearer $MR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "x-mr-session-id: conv_8812" \
  -H "x-mr-correlation-id: job-2026-10-01-0042" \
  -d '{
    "model": "multi-router/rt_9Hk3Ws7PzQ",
    "user": "tenant_acme",
    "messages": [{ "role": "user", "content": "Summarize ticket 4521." }]
  }'

Response headers

Response headers describe how Multi-Router served a request. Every response carries x-mr-request-id, and x-mr-correlation-id when one was sent. Successful responses from Chat Completions and Messages also carry the rest:

HeaderValue
x-mr-request-idThe request id, on every response including errors.
x-mr-correlation-idThe caller's correlation id, when one was sent.
x-mr-providerThe provider that served the request.
x-mr-upstream-modelThe catalog model that served the request.
x-mr-upstream-wire-idThe provider's own model id.
x-mr-regionThe region that served the request, when known.
x-mr-attemptsHow many attempts the request took.
x-mr-composerThe fallback or weighted router, when one handled the request.
x-mr-policyHow the router was chosen. The values are in the next table.
x-mr-model-deprecatedtrue when the model served is deprecated.
x-mr-model-replaced-byThe model that replaces a deprecated model.
x-mr-policyThe router was chosen by
staticA router id in the model field.
model_aliasA built-in model alias in the model field, such as claude-haiku-4-5.
headerThe X-MR-Router header.
fallbackA fallback router.
weightedA weighted router.
passthroughA provider and model name in the model field, such as anthropic/claude-sonnet-4.5.
bareA model name on its own in the model field.

Claude Proxy responses also carry x-mr-upstream-wire-id, and Claude Proxy, Codex Proxy and Gemini Proxy responses pass the provider's own headers through. Adaptive Router responses carry x-mr-rule, the id of the rule that planned the request.

Finding a request

To find a request from an application log:

  1. Log the x-mr-request-id response header, or send an x-mr-correlation-id with each request.
  2. In Traffic, paste the id into the search box, with a time range that covers the request.
  3. Select the request id to open its detail. See Request Detail.

A session id finds every request of a conversation the same way, and the Customers view and the Customer filter show usage for one end customer.

CostOverview
Was this helpful?