Routing
The auto model
Send model auto and DigitSpace picks a model that can handle the request at the quality level you set, from economy to balanced or best.
Send "model": "auto" and DigitSpace picks the model as well as the provider. It considers only models that can do what the request needs, at or above a quality level, and then ranks them with the project's routing strategy.
Quality levels
DigitSpace keeps a list of models for auto, each placed at one of three levels: basic, standard or advanced. The quality you ask for sets the lowest level allowed.
| You send | Models considered |
|---|---|
auto:economy | Basic and above |
auto:balanced | Standard and above |
auto:best | Advanced only |
auto | The project's setting, which is Balanced unless changed |
Set the project's quality under Routing → Auto model quality in the dashboard. A quality in the request overrides it for that request.
Requests that use tools or reasoning always get a standard model or better, even on auto:economy, because small models handle them poorly.
What auto checks
Before ranking, auto drops models that can't serve the request:
- images in the messages need a model with vision;
toolsneed tool support;- a
json_schemaresponse format needs structured output; reasoning_effortneeds reasoning;- the estimated input plus
max_tokensmust fit the context window.
If no model at the level qualifies, auto widens to the rest of its list, and then to every model.
Seeing what was chosen
The response's model field says auto. To see the model and provider that answered, read the x-digitspace-provider header, or open the request in Activity, which shows the model, the quality level used and why.
Exact names after auto: are checked: auto:economy, auto:balanced and auto:best. Anything else after auto: is treated as plain auto across every model, without a quality level, so check the spelling.
Checked against the gateway on 31 October 2026. Something wrong or missing? Tell us.