How we read the signal

Analysis frame

Evidence level

Primary-source evidence

Analytical lens

Separating the broker's own logging from the conduct of the downstream processor shows what an endpoint label can and cannot certify.

Affected groups
  • Developers buying model access through a broker
  • People whose data is included in application requests
What remains unknown
  • Which individual prompts were retained downstream
  • What historical route records customers can obtain
Second-order effects to watch
  • A temporarily narrower set of routes can affect availability or cost.
  • Processor-level records could become a procurement requirement for sensitive work.

What to ask of a routing record

Ask for the model, processor, date, retention policy and any fallback that applied to the past request. The important distinction is between a recorded route and the route the system was supposed to use.

Primary trail

Go to the source

Read the evidence behind this analysis. External links open in a new tab.

OpenRouter — actions on inference-provider incidents Novita — MiniMax request privacy notice