Routing

Choose between shorter and more specific route selectors based on the availability and control you need.

Tresor accepts four route selector forms:

modelId
region/modelId
provider/modelId
region/provider/modelId

The shorter the selector, the more flexibility Tresor has to choose an eligible concrete route for that request. In practice, that usually means higher availability.

Choose the amount of control you need

Selector	What you control	What Tresor can still choose	Availability profile
`modelId`	the model family	provider and region	highest
`region/modelId`	model family and region	provider within that region	high
`provider/modelId`	model family and provider	region for that provider when multiple regions exist	medium
`region/provider/modelId`	model family, region, and provider	nothing	lowest

If you want Tresor to have the most room to keep requests flowing, use the shortest selector that still matches your requirements.

What shorter routes buy you

Shorter routes give Tresor more eligible concrete routes to work with.

kimi-k2.6 gives Tresor the most flexibility for that model.
eu/kimi-k2.6 keeps the request in eu but still lets Tresor choose among eligible providers in that region.
privatemode/kimi-k2.6 keeps the request on Privatemode while allowing multiple Privatemode regions when they exist.
eu/privatemode/kimi-k2.6 pins one exact route.

When more than one concrete route matches your selector, Tresor chooses among the eligible routes for that selector and may move within that selector if the first eligible route cannot be used.

When to pin a full route

Use region/provider/modelId when you need one or more of these to stay fixed:

a specific provider
a specific region
a specific pricing route
a specific prompt-caching or reasoning contract

If you do not need that level of control, prefer a shorter selector.

How to inspect available routes

Use GET /v1/models?detail=true to inspect published route selectors, concrete routes, pricing, prompt caching, and reasoning details.