Platform

Message capture

Opt-in conversation capture: encrypted, retention-capped, deletable.

By default TokenRouter stores no prompt or response bodies — request logs carry token counts, cost, and latency only. Message capture flips that for exactly the traffic you choose: opt an API key, a team, or a member in, and their conversations become reviewable in Transcripts and usable for monitors and evals.

How scopes combine

Capture scopes are a union: a request is captured when any covering scope — its key, its team, or its member — has capture enabled. Enable it from Settings → Data capture, or flip the switch on an individual API key. Changes reach the gateway within a minute.

What gets stored, and how

• The request body and the final assembled response — exactly what the client sent and received, including on byte-exact passthrough surfaces.
• Bodies are compressed and encrypted (authenticated encryption, same vault as your provider keys) before they leave the API process. Oversized content — base64 images, giant payloads — is truncated at capture time with a visible marker.
• Capture is best-effort by design: it can never fail, slow, or alter a request, and it never touches streaming wire formats.

Retention

You can set a shorter window than your plan allows. Downgrading shortens retention retroactively — the next sweep deletes anything beyond the new cap. Admins can also purge all captured data instantly from Settings. Dataset items are snapshots, so purges and sweeps never break your evals.