Outborn Agent Platform · Manual
Model routing
Configure multiple runtime/model sources with clear priority, automatic selection, and controlled fallback.
Applied guidance
Best practices for model routing
Recommended
- Set an explicit preferred source and permitted fallback order.
- Check each fallback's credentials, policy, model, and billing separately.
Avoid
- Do not assume a failed authorization can be repaired by automatic fallback.
How it fits together
01
Configure sources
Add one or more eligible runtime sources to the agent or configuration. Each source keeps its own account, model, enabled state, and usage boundary.
02
Priority
Priority controls which source is preferred first when more than one source can handle the request.
03
Automatic routing
Automatic routing may choose among eligible sources based on the configured routing policy and runtime availability.
04
Fallback
Fallback proceeds only to another configured and permitted source. A fallback does not convert Provider Subscription into Provider API or vice versa.
05
Important limitations
A model may be unavailable because of provider support, account entitlement, regional availability, organization policy, temporary provider state, or exhausted allowance.
Related documentation