Provider Logging
How to keep traffic on providers that match your data policy
Each upstream provider has its own retention and training policy. TheRouter.ai does not evaluate those policies per request, so the way to match your organization's risk profile is to review the providers yourself and restrict routing to the ones you have approved.
Restrict routing to approved providers
List approved provider brands in provider.only (or exclude brands with provider.ignore) and set allow_fallbacks: false so the request fails instead of reaching a provider outside the list.
TypeScript
const body = {
model: "anthropic/claude-sonnet-4.5",
messages: [{ role: "user", content: "Review this contract" }],
provider: {
only: ["anthropic"],
allow_fallbacks: false,
},
};No automatic data-policy filter
The
data_collection and require_parameters fields are accepted for client compatibility but do not change routing. Setting data_collection: "deny" does not exclude any provider; use only or ignore instead.Operational caveats
Availability tradeoff
A shorter provider list leaves fewer routes to fail over to. Configure explicit fallback models so policy compliance does not turn into avoidable downtime.
Document approved providers and review their terms on a recurring cadence. A policy that was compliant last quarter may change with new model or provider terms.