Automatically route sub-questions within a conversation to the most capable specialist model.
Not yet available. The Advisor server tool is not yet available.
Advisor watches the conversation as it unfolds and, when it detects a sub-question that a specialist model would answer better than the primary model, it routes that question to the specialist, injects the answer back into the context, and lets the primary model continue. Your application makes one API call and receives one response.
In this example, when the primary model reaches the code portion of its response, Advisor detects the code intent and routes that sub-task to claude-opus-4.8. The result is injected back into the context before gpt-5.4 continues writing the surrounding prose.
| Slot | Description |
|---|---|
code | Programming, debugging, code review |
math | Numerical reasoning, equations, statistics |
vision | Image description or analysis |
search | Live web retrieval (pairs with opendunes.web_search) |
default | Fallback for any sub-task not matched above |
All slots are optional. Unmatched sub-tasks stay with the primary model.
| Option | Type | Default | Description |
|---|---|---|---|
specialists | object | {} | Slot-to-model-slug mapping |
min_confidence | number | 0.7 | Minimum routing confidence before delegating (0–1) |
max_hops | integer | 3 | Maximum specialist calls per request |
Each specialist invocation is billed at the specialist model's DA rate. The primary model is billed for the full conversation including injected specialist results. All hops are itemized in the per-request usage breakdown.