Begin with retained evidence
The Insights center evaluates current controls and retained request metadata for setup gaps, concentration, degraded supply, elevated failures, and eligible routing improvements without reading prompt or response bodies.
Separate action from health
Filter the queue by readiness, cost, reliability, governance, or security. Each item states the observed evidence and links to the control surface an administrator should examine.
Review the exact route
The first automated cost recommendation applies only when a priority-and-weight route already has multiple approved, enabled targets with different valid modeled prices. It does not add a provider or model.
See the one changed field
Open the server-generated preview and confirm the route version and only proposed change: target selection becomes cost optimized. Provider, model, retry, timeout, budget, policy, capability, and region settings remain unchanged.
Retain audit and rollback
A successful approval creates a new route release and before-and-after audit evidence. The prior release remains available for an explicit, revalidated rollback instead of an unaudited configuration overwrite.
Collect bounded outcome evidence
Route history compares bounded seven-day windows around the approved release, capped by adjacent changes. It reports cost, recorded tokens, latency, failures, fallbacks, and exact-versus-conservative usage coverage.
Do not invent savings or quality
The comparison labels collecting, indicative, reviewable, and bounded-scan states. It does not claim causal savings or infer output quality because workload mix and provider conditions can differ between windows.