Custom models

Custom models create stable ctm: aliases that can route to one or more provider models, specific accounts, weighted target sets, or fallback chains.

Before you start

Confirm the target provider accounts are healthy and visible in the dashboard. If the alias will be exposed to clients, make sure each target provider/account is allowed by the relevant API keys; keys do not have alias-specific allow-lists.

Create an alias

1. 1
   Open Custom Models in the dashboard.

   This section manages aliases that clients call as ctm:name.

2. 2
   Choose a stable name.

   Use an operational name such as ctm:workhorse, ctm:research, or ctm:fast.

3. 3
   Add provider targets.

   Each target points to a provider model and can optionally select a specific account.

4. 4
   Set weights and fallback order.

   Use weighting for distribution and fallback order for controlled failover.

5. 5
   Save and test.

   Run a Test API prompt before publishing the alias.

Supported behavior

• Multiple provider targets Route one alias to several providers or models.
• Specific account targeting Pin a target to one upstream account when needed.
• Account exclusion Use every account except a selected account for maintenance or isolation.
• Weighted load balancing Give preferred targets more traffic while keeping backups available.
• Fallback chains Try another target when a provider fails, cools down, or runs out of quota.

Example

{
  "model": "ctm:research",
  "targets": [
    { "model": "cld:claude-sonnet-4", "weight": 3 },
    { "model": "gem:gemini-3-pro", "weight": 1 },
    { "model": "glm:glm-4.5", "weight": 1 }
  ]
}