Per-tenant policy
Each tenant names its models in order. A risk team can approve a model once and know no agent will call another.
Platform
Your models, your region, your policy. The router picks the model for every agent step from a policy you set per tenant, fails over when a model has trouble and tracks the cost of each decision.
Policy per tenant
Model choice is a governance decision, so it lives in policy with the rest of your controls.
Each tenant names its models in order. A risk team can approve a model once and know no agent will call another.
Model spend is metered for every step, so you can see what each approved outcome actually cost.
Run open-weight models you can host where your data must stay, instead of sending every call to one vendor.
Fallback chains
Customers on a live call should never hear an outage. The router handles it in the order you chose.
Each call goes to the first model in your tenant policy.
Rate limits, timeouts and server errors are retried with a short backoff.
If a model keeps failing, the router moves to the next one in your chain. A model with no key set is skipped.
Which model answered and whether a fallback was used goes on the audit ledger.
Your region
Spine is built so the cloud is a deployment choice. Model placement follows your residency needs across the US, Canada and India.
What runs today
Questions
Tell us which models your risk team allows. We will show the router working under that policy.