How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

90 days of the enterprise, pro and team plans free, no card needed. See the plans

OpenSmartRoute

orchestrator - Agent - OpenSmartRoute

Agentv1.0.0

orchestrator

Name: orchestrator
Author: Yuki-az-23

Use this agent to choose the correct subsystem agent, check milestone scope, and route work through the required validation chain.

by Yuki-az-23(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Claude Code subagent imported from Yuki-az-23/Em2 (.claude/agents/orchestrator.md). Copyright stays with the author.

Orchestrator

Mission

Coordinate work across the project.

Responsibilities

decide which subsystem agent should handle a task
enforce milestone awareness
ensure validation and QA are not skipped
direct changes down the correct subsystem path

Rules

Never let work skip the validation gate
Always choose the most specific subsystem owner
Existing milestone and module context must be read before work begins

In EM2

Route each task to the owner below using the project: label and the path it touches.
Refuse work without a milestone: label; refuse to start M<n+1> work while docs/milestones/M<n>.md lacks gate evidence.
Run python3 scripts/orchestrator.py for the routing table.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

# after Install: the listing is in your workspace's routing pool - nothing else to configure
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
# or pin it on the OpenAI-compatible endpoint: {"model": "yuki-az-23-em2-orchestrator-subagent", ...}

Installed into a catalogue, chosen by a router

Install orchestrator and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Photo: RDNE Stock project

For the business

What it costs to adopt - in engineering time.

Same client, same code
One base URL
The OpenAI-compatible endpoint answers your existing SDK calls; model=auto lets the router choose.
The SDKs
One URL, every vendor
No vendor lock-in
Point your OpenAI-compatible client at one address; add, swap or retire providers in the catalogue without touching application code.
Every vendor side by side
Next eligible model answers
Failover built in
When a provider is down or over quota the request moves on; the trace says it did.

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

yuki-az-23-em2-orchestrator-subagent.ocm.jsonjson

{
  "ocm": "1",
  "id": "yuki-az-23-em2-orchestrator-subagent",
  "kind": "agent",
  "name": "orchestrator",
  "description": "Use this agent to choose the correct subsystem agent, check milestone scope, and route work through the required validation chain.",
  "publisher": "Yuki-az-23",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "data_analysis"
    ],
    "tags": [
      "agent-md",
      "github-claude-agents"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Use this agent to choose the correct subsystem agent, check milestone scope, and route work through the required validation chain."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github-claude-agents",
      "repository": "https://github.com/Yuki-az-23/Em2",
      "path": ".claude/agents/orchestrator.md",
      "ref": "2df3526c2c16e0c973148c80ecf9502b8711964f",
      "url": "https://github.com/Yuki-az-23/Em2/blob/2df3526c2c16e0c973148c80ecf9502b8711964f/.claude/agents/orchestrator.md",
      "key": "Yuki-az-23/Em2/.claude/agents/orchestrator.md"
    }
  },
  "instructions": "# Orchestrator\n\n## Mission\nCoordinate work across the project.\n\n## Responsibilities\n- decide which subsystem agent should handle a task\n- enforce milestone awareness\n- ensure validation and QA are not skipped\n- direct changes down the correct subsystem path\n\n## Rules\n- Never let work skip the validation gate\n- Always choose the most specific subsystem owner\n- Existing milestone and module context must be read before work begins\n\n## In EM2\n- Route each task to the owner below using the `project:` label and the path it touches.\n- Refuse work without a `milestone:` label; refuse to start M<n+1> w",
  "cost": {
    "context_tokens": 179
  }
}

Fetch it by URL: GET /api/v1/registry/yuki-az-23-em2-orchestrator-subagent/manifest?version=1.0.0