Let OpenDunes automatically select the best model for each request based on the prompt content.
Not yet available.
The Auto Router removes the model selection decision from your code entirely. Set model to "opendunes/auto" and OpenDunes analyzes the prompt, infers the task type, and routes to the best available model — balancing accuracy, cost, and latency in real time.
The model field in the response tells you which model was chosen. Every other field in the response is identical to a direct model request.
The Auto Router runs a fast classification step on the prompt before dispatching it. It considers:
The classification step adds less than 100ms of overhead in most cases.
By default, the Auto Router picks the best model across all cost tiers. To constrain the selection to a budget, pass max_cost_da per request:
You can also set a default cost ceiling for all Auto Router requests in your dashboard under Settings → Routing defaults.
Because the router selects the model dynamically, the DA cost per request varies. The model field in the response always tells you what ran. The usage field gives you the exact token counts, which you can cross-reference with the catalog's DA pricing to understand the cost.
The router does not currently expose a "why did you pick this" field — the selected model is the only output. This may change.
If there are models you never want the Auto Router to choose — for compliance, budget, or quality reasons — add them to your account's router exclusion list in the dashboard. Excluded models are skipped regardless of classification result.
You pay the selected model's standard per-token DA rate. The Auto Router itself has no additional charge. Requests routed to cheap models cost less; requests routed to frontier models cost more. Use max_cost_da to keep variance predictable.
Note. The Auto Router is designed for general workloads. For accuracy-critical tasks, use Auto Exacto. For cost-critical workloads, use the Free Models Router.