Omni Combos Routing
Create and manage routing combos with every strategy (priority, weighted, round-robin, Auto-combo, and more). Configure fallback chains, test routing outcomes, and retrieve combo metrics.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Omni Combos Routing when an AI agent needs a reusable SKILL.md workflow for this job: Create and manage routing combos with every strategy (priority, weighted, round-robin, Auto-combo, and more). Configure fallback chains, test routing outcomes, and retrieve combo metrics.
When not to use it
Skip Omni Combos Routing when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/omni-combos-routing # Save SKILL.md to ~/.claude/skills/omni-combos-routing/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/omni-combos-routing/SKILL.md. For a shared project, commit the folder at .claude/skills/omni-combos-routing/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Omni Combos Routing skill for this task: Use Omni Combos Routing when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeinferred
The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- chatgptinferred
The skill text mentions ChatGPT or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- geminiinferred
The skill text mentions Gemini or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->
## Overview
Create and manage routing combos with every strategy (priority, weighted, round-robin, Auto-combo, and more). Configure fallback chains, test routing outcomes, and retrieve combo metrics.
## Authentication
All requests require a valid Bearer token or session cookie. Obtain a token via `POST /api/auth/login` or configure `REQUIRE_API_KEY=false` for local development.
## Endpoints
### GET /api/combos
List routing combos
```bash curl http://localhost:20128/api/combos \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### POST /api/combos
Create routing combo
```bash curl -X POST http://localhost:20128/api/combos \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### GET /api/combos/{id}
Get combo by ID
```bash curl http://localhost:20128/api/combos/{id} \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### PUT /api/combos/{id}
Update combo
Partial update: the body is merged onto the stored combo, so a field left out keeps its current value. An array that IS sent replaces the stored one outright.
```bash curl -X PUT http://localhost:20128/api/combos/{id} \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### PATCH /api/combos/{id}
Update combo
Partial update: the body is merged onto the stored combo, so a field left out keeps its current value. An array that IS sent replaces the stored one outright.
```bash curl -X PATCH http://localhost:20128/api/combos/{id} \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### DELETE /api/combos/{id}
Delete combo
```bash curl -X DELETE http://localhost:20128/api/combos/{id} \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/combos/metrics
Get combo metrics
```bash curl http://localhost:20128/api/combos/metrics \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### POST /api/combos/test
Test a combo configuration
```bash curl -X POST http://localhost:20128/api/combos/test \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### GET /api/fallback/chains
List fallback chains
Returns all registered fallback chains for model routing.
```bash curl http://localhost:20128/api/fallback/chains \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### POST /api/fallback/chains
Create fallback chain
Registers a fallback routing chain for a model.
```bash curl -X POST http://localhost:20128/api/fallback/chains \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### DELETE /api/fallback/chains
Delete fallback chain
```bash curl -X DELETE http://localhost:20128/api/fallback/chains \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/combos/auto
GET combos › auto
```bash curl http://localhost:20128/api/combos/auto \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/combos/builder/options
GET combos › builder › options
```bash curl http://localhost:20128/api/combos/builder/options \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### POST /api/combos/duplicate
POST combos › duplicate
```bash curl -X POST http://localhost:20128/api/combos/duplicate \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### POST /api/combos/reorder
POST combos › reorder
```bash curl -X POST http://localhost:20128/api/combos/reorder \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
## Payloads
See the full OpenAPI specification at `GET /api/openapi/spec` or `docs/openapi.yaml` for detailed request/response schemas.
<!-- skill:custom-start --> <!-- Migrated from skills/omniroute-routing/SKILL.md (preserved curated content) -->
# OmniRoute — Routing & Combos
Requires `OMNIROUTE_URL` and `OMNIROUTE_KEY`. See [entry-point SKILL](https://raw.githubusercontent.com/cheaper-inference/OmniRoute/main/skills/omni-auth/SKILL.md) for setup.
## What is a combo?
A combo is a named group of providers/models with a routing strategy. All requests through a combo are automatically distributed, failed-over, and load-balanced — the caller uses a single model ID like `my-combo`.
## List existing combos
```bash curl $OMNIROUTE_URL/api/combos \ -H "Authorization: Bearer $OMNIROUTE_KEY" ```
Response includes `id`, `name`, `strategy`, `enabled`, and per-target stats.
## Create a combo
```bash curl -X POST $OMNIROUTE_URL/api/combos \ -H "Authorization: Bearer $OMNIROUTE_KEY" \ -H "Content-Type: application/json" \ -d '{ "name": "my-combo", "strategy": "priority", "targets": [ { "provider": "anthropic", "model": "claude-opus-4-7", "weight": 1 }, { "provider": "openai", "model": "gpt-4o", "weight": 1 } ] }' ```
## Public routing strategies
The public set is `ROUTING_STRATEGY_VALUES` in `src/shared/constants/routingStrategies.ts`; the table names each one.
| Strategy | Description | | --- | --- | | `priority` | Always use target[0]; fall back on error | | `weighted` | Distribute by weight percentage | | `round-robin` | Rotate targets in order | | `context-relay` | Chain models for very long contexts | | `fill-first` | Fill quota of target[0] before spilling | | `p2c` | Power-of-two choices: sample two targets, pick the better candidate | | `random` | Uniform random selection | | `least-used` | Route to the target with the lowest observed usage | | `cost-optimized` | Pick the cheapest eligible target for the token estimate | | `reset-aware` | Prefer targets based on quota-reset state | | `reset-window` | Order targets by their configured reset window | | `expiry-first` | Spend the account whose quota would expire unused first — highest leftover, nearest reset | | `headroom` | Prefer targets with more remaining quota headroom | | `quota-weighted` | Skip exhausted accounts; pick among the rest in proportion to leftover quota over in-flight load | | `strict-random` | Random without repeating until all targets have been used | | `auto` | Auto-Combo multi-factor scoring | | `lkgp` | Last-known-good-provider sticky routing | | `context-optimized` | Pick the best model for the request's context size | | `cache-optimized` | Prefer targets with stronger cache affinity | | `fusion` | Run a panel in parallel and synthesize one judged response | | `pipeline` | Run a configured sequence of targets as a pipeline |
## Auto-combo (recommended for production)
Auto-combo scores every candidate on each request with its multi-factor model (factors and weights: `DEFAULT_WEIGHTS` in `open-sse/services/autoCombo/scoring.ts`):
```bash curl -X POST $OMNIROUTE_URL/api/combos \ -H "Authorization: Bearer $OMNIROUTE_KEY" \ -H "Content-Type: application/json" \ -d '{ "name": "prod-auto", "strategy": "auto", "targets": [ { "provider": "anthropic", "model": "claude-sonnet-4-6" }, { "provider": "openai", "model": "gpt-4o-mini" }, { "provider": "google", "model": "gemini-2.0-flash" } ] }' ```
Then call it with:
```bash curl -X POST $OMNIROUTE_URL/v1/chat/completions \ -H "Authorization: Bearer $OMNIROUTE_KEY" \ -H "Content-Type: application/json" \ -d '{ "model": "prod-auto", "messages": [{ "role": "user", "content": "Hello" }] }' ```
## Activate / deactivate a combo
```bash # Activate curl -X PUT $OMNIROUTE_URL/api/combos/{id} \ -H "Authorization: Bearer $OMNIROUTE_KEY" \ -H "Content-Type: application/json" \ -d '{ "isActive": true }' ```
## Get combo metrics
```bash curl "$OMNIROUTE_URL/api/combos/metrics?combo=<name>" \ -H "Authorization: Bearer $OMNIROUTE_KEY" ```
Returns p50/p95/p99 latency, success rate, cost, and per-target breakdown.
## Simulate routing (dry run)
```bash curl -X POST $OMNIROUTE_URL/api/playground/simulate-route \ -H "Authorization: Bearer $OMNIROUTE_KEY" \ -H "Content-Type: application/json" \ -d '{ "comboId": "{id}", "promptTokens": 1000 }' ```
Returns which provider would be selected and why — no actual API call is made.
## Via MCP (if OmniRoute is your MCP server)
``` omniroute_list_combos → list all combos omniroute_switch_combo → enable/disable a combo omniroute_set_routing_strategy → change strategy at runtime omniroute_simulate_route → dry-run routing decision omniroute_best_combo_for_task → get recommendation by task type ```
## Errors
- `404 combo not found` → check `id` from `/api/combos` - `400 invalid strategy` → use one of the strategies above - `409 name conflict` → combo name already exists <!-- skill:custom-end -->
Intended uses
- Use Omni Combos Routing when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.