Combos

--- title: "Combos" description: "Expose an ordered model fallback chain as one selectable model name." icon: "git-branch" ---

Overview

Combos publish a named model chain. A client sends the combo name as model; Aurora calls the first model as primary and uses the remaining models as ordered fallback targets.

Use combos when application code should call one stable model name while operators control the primary model and fallback sequence centrally.

Manual management

Use the dashboard at Combos to create, edit, disable, and delete combos. Add providers first, confirm real selectors in GET /admin/api/v1/models, then build the combo from those selectors.

coding-default
  primary:  <provider-name>/<primary model id>
  fallback: <provider-name>/<fallback model id>

Clients call the combo by name:

{
  "model": "coding-default",
  "messages": [{"role": "user", "content": "Review this function."}]
}

Server API automation

For endpoint reference see the Admin API section.

curl -X POST http://your-aurora-host/admin/api/v1/combos \
  -H "Authorization: Bearer $AURORA_MASTER_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "coding-default",
    "description": "Default coding chain",
    "enabled": true,
    "models": [
      "<provider-name>/<primary model id>",
      "<provider-name>/<fallback model id>"
    ]
  }'

Use real selectors from /admin/api/v1/models. Combos are routing policy, not provider credentials.