Auto Router

​

Usage

response = client.chat.completions.create(
  model="clearmaas/auto",
  messages=[{"role": "user", "content": "..."}],
)

const response = await openai.chat.completions.create({
model: "clearmaas/auto",
messages: [{ role: "user", content: "..." }],
});

​

Default behavior

• Pattern: empty — matches every chat model your account has access to. New models that come online become candidates automatically.
• Strategy: cheapest — picks the model with the lowest per-token price among live candidates.
• Default model: none. If the pattern resolves to no available models, the request fails with a clear error. You can set a default in the dashboard if you want a safety net.

​

When to prefer Auto Router over explicit model names

• You don’t want to pin to a specific model; you want the cheapest live chat model at each request.
• You’re prototyping and don’t want to care about which provider is up.
• You want ClearMaas’s routing to “just work” without thinking about it.

​

When to prefer explicit model names

• You need deterministic output — picking different models at different times will change generation style and quality.
• You’re using features specific to one model (e.g. Claude’s cache_control, or a model’s native image generation).
• You want predictable per-request cost.

​

Seeing what Auto Router picked

res = client.chat.completions.with_raw_response.create(
    model="clearmaas/auto", ...
)
actual_model = res.headers.get("X-Clear-Resolved-Model")
# e.g. "openai/gpt-4o-mini"