Skip to main content
The first slash in model distinguishes a direct provider reference from a task alias.

Task aliases

The proxy reads routing for version 1, chooses among targets with positive weights, replaces model, and calls the target’s provider.

Version pins

A pin resolves exactly version 3. It never falls forward to the latest version and never changes version 1. This makes a new version safe to test before application rollout.

Direct provider calls

The prefix before the first slash selects a provider in the resolved W&B entity. The remainder is the configured provider model ID; additional slashes are allowed. Direct calls are useful for relabeling, judges, ad hoc comparisons, and validating provider setup. They bypass task weights and receive no task identity.

Entity resolution

The bearer key’s default entity is used unless the body contains:
The requested value must be the caller’s personal/default entity or one of their W&B teams.

Sticky weighted selection

Provide a conversation ID to keep all calls in one conversation on the same target for a routing revision:
Changing the routing revision can intentionally move that key to a different target.
Use alias@vN in model. A direct provider call uses provider/model-id instead.
See Create a routed chat completion for the complete schema.
Last modified on August 25, 2026