Routing
Router Settings
Parameter defaults, prompt bindings, request logging, tags and descriptions, and which router types use each.
Router settings are the behavior a router applies to every request beyond choosing a model: default request parameters, a bound prompt, what Traffic records, and the labels used to find and group routers. Settings apply to requests after they change, with no change to callers. Which settings a router has depends on its type:
| Setting | Static router | Adaptive Router | Fallback, weighted | Claude, Codex and Gemini Proxy |
|---|---|---|---|---|
| Parameter defaults | Yes | No | From the serving member | No |
| Prompt binding | Yes | Named bindings, chosen by rule or header | From the serving member | No |
| Request logging | Yes | Yes | From the serving member | Yes |
| Tags | Yes | Yes | Yes | Yes |
| Description | Yes | Yes | Yes | Yes |
Parameter defaults
Parameter defaults are request parameters a static router fills in when a request leaves them out, on both Chat Completions and Messages. The caller's value always wins, and a parameter sent as null or an empty stop list counts as left out. Messages requires max_tokens in every request, so the Max tokens default applies to Chat Completions. Parameter defaults are set in the Settings panel of the router's page under Parameter defaults, with Stop sequences entered as a comma-separated list, and saved with Save settings.
| Field | Dashboard label | Values |
|---|---|---|
temperature | Temperature | 0 to 2 |
max_tokens | Max tokens | 1 or more |
top_p | Top P | 0 to 1 |
seed | Seed | A whole number |
presence_penalty | Presence penalty | -2 to 2 |
frequency_penalty | Frequency penalty | -2 to 2 |
reasoning_effort | Reasoning effort | none, minimal, low, medium, high, xhigh |
verbosity | Verbosity | low, medium, high |
response_format | Response format | text, json_object |
tool_choice | Tool choice | none, auto, required |
parallel_tool_calls | Parallel tool calls | true or false |
stop_sequences | Stop sequences | Up to 10, each up to 200 characters |
Prompt binding
A prompt binding attaches a saved prompt to a static router, so every request through the router carries it. The prompt is an inline prompt or a file in a connected GitHub repository, and the binding either tracks its latest revision or is pinned to a revision number or commit. A text prompt combines with the caller's system message according to Prompt composition; the caller's system message is the first message, when its role is system. A chat prompt's messages are inserted before the conversation as written and replace the caller's system message, and Prompt composition does not apply to it.
| Prompt composition | Value | Behavior |
|---|---|---|
| Merge | merge | The router's prompt comes first, followed by the caller's system message; on Messages the two stay separate blocks. This is the dashboard's default. |
| Override | override | Only the router's prompt applies, and the caller's system message is dropped. |
| Fallback | fallback | The caller's system message applies when present; otherwise the router's prompt applies. |
A prompt with {{variables}} takes their values from the request's prompt_variables object on Chat Completions and Messages, and a missing variable returns missing_prompt_variables. See Prompt Variables. In the dashboard, the Prompt panel shows the Source, Prompt, Revision and Prompt composition, with Bind or Edit to choose the prompt, and the Bind a prompt panel offers Track latest or Pin to a specific revision. See Prompt Binding.
Request logging
Request logging sets what Traffic records about each request a router serves: Request metadata (None, Failures only, Anonymous Metadata or Full Metadata) and Request payloads (None, Failures only, Sample or All Payloads), with a sample percentage for Sample. A router's logging is capped by the administrator's Storage Policy, options above the cap show as Administrator managed, and the sample percentage cannot exceed the administrator's limit. Request payloads record no more than Request metadata allows: None turns payloads off, and Failures only limits payloads to failures. A router that has never been changed follows the Storage Policy. See Observability for what each level records and how to view it.
Tags
Tags are labels that group routers. A router carries up to 20 tags of up to 80 characters each; tags are stored in lowercase without duplicates, and contain no # or control characters. Budgets can be scoped to routers by tag, and the Routers page lists tags in its views rail and filters by them. The prefixes person: and policy: are reserved for routers created by tools policies. Tags are set in the dashboard, and an alias has no tags of its own.
Description
A description is free text about what a router is for and who owns it, up to 500 characters, shown on the router's page and edited with the pencil next to it.