Tarseek API
Providers & deployments
One canonical model can have many deployments. Tarseek chooses a deployment unless you constrain routing in the project.
Default routing
Eligible deployments are those that are enabled, healthy, allowed by your project rules, and within your price ceiling. Tarseek then failovers across remaining deployments of the same model when a provider fails. After the first streamed byte, Tarseek does not fail over to another provider; see Streaming.
Routing controls
| Control | Behavior |
|---|---|
| Automatic selection | Default. There is no separate tarseek/auto model ID. |
| Price ceiling | Project setting. Tarseek does not currently optimize for “always cheapest.” |
| Allow / block lists | Project routing page. |
| Availability / circuit breaker | Automatic. |
| Provider preference on the request | Not a public request field today. |
| Latency-based selection | Not offered today. |