Review provider inventory, benchmark evidence, route policy, and recommendation flow in the signed-in providers surface.
Use this guide when you need to understand how SerenQuant evaluates provider capability, benchmark evidence, and route policy before a provider becomes the default for a route family.
The provider page combines inventory, policy, benchmark, and evidence surfaces into one operating view.
Review the provider profiles and account or entitlement context that determine what the workspace can use.
Inspect coverage, quality tier, support flags, and enabled state across provider capability rows.
Edit or review route-policy behavior that controls which provider is preferred for a route family.
Use benchmark runs, result filters, and recommendation badges to evaluate provider quality and latency tradeoffs.
Review recommendation outcomes, latest route decisions, and usage rows before treating a change as stable.
Export the capability matrix and preserve the evidence trail around provider configuration changes.
Use this loop to keep provider changes evidence-based instead of intuition-driven.
Start by confirming profiles, entitlements, and capability rows so you know what the workspace can actually route through.
Use benchmark results, coverage, latency, and drift metrics before treating a provider as preferred.
Change route policies only after the recommendation flow and route-decision evidence point the same way.
Capture exports, usage, and recent decisions so the provider change can be audited later.
The capability matrix is where provider posture stops being abstract and becomes route-by-route operating reality.
The capability matrix lets you downgrade or upgrade quality expectations by route family. Read those selectors before changing a default provider.
Use enabled flags to control which capability rows can participate in routing. Disabled rows should reflect intentional policy, not stale config.
Each row carries provider, data kind, asset class, scope, and interval context. Validate that scope coverage matches the route family you plan to benchmark.
Keep the entitlement card beside the matrix in mind. A strong capability row is not actionable if the workspace cannot actually access that provider.
The policy editor is where benchmark evidence becomes an actual routing change.
Use the draft form to pin data kind, asset class, region, market segment, interval, and quality tier before you assign a primary provider.
Set the primary provider and fallback chain together so route behavior is predictable when the preferred source is degraded.
Best-effort is a conscious tolerance decision. Pair it with enabled state so exceptions are explicit instead of accidental.
Review the existing policy rows after each change. They are the operational truth for what the router will actually do.
Use these playbooks when provider benchmarking needs to translate into a governed routing decision.
Review capability rows, benchmark runs, recommendation badges, and route-decision history together before changing the preferred provider for a route family.
The provider change is backed by evidence from both synthetic benchmarks and recent routing behavior instead of one isolated signal.
When the preferred source looks unstable, adjust the primary and fallback chain together, then confirm the updated behavior through preview output and recent live decision rows.
The route family keeps serving through a deliberate fallback posture rather than relying on accidental best-effort behavior.
Open the Why this decision drawer and usage evidence when the recommended provider is high quality but expensive, then compare that against entitlements and current route usage.
You can explain whether the workspace should keep paying for the recommended path or step down to a more sustainable provider tier.
Jump into the signed-in providers page and inspect profiles, capabilities, benchmarks, and route policies.
See how provider choices feed into live, paper, broker, and realism execution workflows.
Review the workspace policy and runtime settings that shape provider use and production posture.
Mar 24, 2026
Report unclear guidance, stale contracts, missing coverage, or broken docs UI on this page.
Open feedback issueJump to the section you need without losing your place.
Mar 24, 2026
Report unclear guidance, stale contracts, missing coverage, or broken docs UI on this page.
Open feedback issue