Skip to content
Get API Key

Navigation

← Documentation

Models & Routing

Choose providers, operators and eligible fallbacks for your requests.

Search guides and API reference.

Documentation sections

Model Selection

Choose a model ID from the live model catalog. Router resolves eligible direct providers, your BYOK credentials and operators. Availability depends on the model, credentials, funded access and requested capabilities. BYOK uses your credential and never falls back to a Router-funded provider or operator.

Routing Strategy

Operator selection considers latency, uptime and price. Provider selection also honors provider order, price ceilings and compliance constraints. Use X-Tangle-Routing to choose operator, provider or auto routing; X-Tangle-Operator pins an operator.

Fallbacks

Retries can exhaust eligible operators or providers and return an error. Pins, BYOK and compliance rules constrain attempts. Router-chosen cross-model substitution requires explicit provider.allow_fallbacks: true and eligible routing; omitting require_model alone does not enable it. Set require_model: true to forbid Router-chosen substitution. Caller-supplied model chains and compatibility aliases are separate behaviors. Read X-Tangle-Served-Model to identify the model that answered.

Routing Controls

bash
# Pin an operator (address or slug)
X-Tangle-Operator: <operator-address-or-slug>

# Select the direct-provider lane
X-Tangle-Routing: provider

In the JSON body, provider.data_residency: 'eu' constrains eligible direct providers; combining residency with operator-only routing is rejected. Use provider.max_price with prompt and completion fields for price ceilings in USD per million tokens. The equivalent gateway fields are providerOptions.gateway.dataResidency and providerOptions.gateway.maxPrice. Residency requests select configured compliance records; they do not independently attest provider behavior.