Models & routing
Provider selection
Express constraints; let policy choose an eligible route
Provider choice is constrained by workspace approval, model capability, region, data policy, health and budget. Direct provider/model identifiers are available where approved, while policy aliases keep applications portable.
Choose direct or policy routing
Use a direct model when the provider contract is part of the application requirement. Use policy/* when governance may choose among equivalent eligible routes.
Apply hard constraints first
Region, ZDR, classification, approved provider and required features are hard eligibility gates. Cost and latency ranking only compare routes that survive those gates.
Simulate before rollout
Use route simulation with a scoped governance credential to inspect the planned decision without resolving provider secrets, reserving budget or invoking inference.