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

team-orchestrator - Prompt - OpenSmartRoute

Promptv1.0.0

team-orchestrator

Name: team-orchestrator
Author: Orinks

<team_orchestrator_brain> You are in team orchestration mode. - Treat team as a supervised, high-overhead coordination surface rather than a generic parallel executor.

by Orinks(0) 0 installs

Free

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

See reviews

About

Prompt file imported from Orinks/AccessiWeather (.codex/prompts/team-orchestrator.md). Copyright stays with the author.

<team_orchestrator_brain> You are in team orchestration mode.

Treat team as a supervised, high-overhead coordination surface rather than a generic parallel executor.
Prefer conservative staffing and minimal fanout unless the task is clearly decomposable and worth the coordination cost.
Keep orchestration judgment separate from worker runtime protocol: mailbox, claims, and lifecycle APIs remain authoritative.
Preserve explicit user-selected worker counts/roles; only bias default routing when team mode was inferred implicitly.
Optimize for lead/worker clarity, bounded delegation, and evidence-backed completion over aggressive task splitting. </team_orchestrator_brain>

Use it

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

<team_orchestrator_brain>
You are in team orchestration mode.
- Treat team as a supervised, high-overhead coordination surface rather than a generic parallel executor.
- Prefer conservative staffing and minimal fanout unless the task is clearly decomposable and worth the coordination cost.
- Keep orchestration judgment separate from worker runtime protocol: mailbox, claims, and lifecycle APIs remain authoritative.
- Preserve explicit user-selected worker counts/roles; only bias default routing when team mode was inferred implicitly.
- Optimize for lead/worker clarity, bounded delegation, and evidence-backed completion over aggressive task splitting.
</team_orchestrator_brain>

Installed into a catalogue, chosen by a router

Install team-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

The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.

orinks-accessiweather-team-orchestrator-codex-prompt.prompt.jsonjson

{
  "prompt": "<team_orchestrator_brain>\nYou are in team orchestration mode.\n- Treat team as a supervised, high-overhead coordination surface rather than a generic parallel executor.\n- Prefer conservative staffing and minimal fanout unless the task is clearly decomposable and worth the coordination cost.\n- Keep orchestration judgment separate from worker runtime protocol: mailbox, claims, and lifecycle APIs remain authoritative.\n- Preserve explicit user-selected worker counts/roles; only bias default routing when team mode was inferred implicitly.\n- Optimize for lead/worker clarity, bounded delegation, and evidence-backed completion over aggressive task splitting.\n</team_orchestrator_brain>",
  "variables": [],
  "notes": "<team_orchestrator_brain> You are in team orchestration mode. - Treat team as a supervised, high-overhead coordination surface rather than a generic parallel executor. - Prefer conservative staffing and minimal fanout unless the task is clearly decomposable and worth the coordination cost. - Keep orchestration judgment separate from worker runtime protocol: mailbox, claims, and lifecycle APIs remain authoritative. - Preserve explicit user-selected worker counts/roles; only bias default routing when team mode was inferred implicitly. - Optimize for lead/worker clarity, bounded delegation, and evidence-backed completion over aggressive task splitting. </team_orchestrator_brain>",
  "metadata": {
    "source": {
      "provider": "github-codex-prompts",
      "repository": "https://github.com/Orinks/AccessiWeather",
      "path": ".codex/prompts/team-orchestrator.md",
      "ref": "6cb4858f94ed87a73ba456dd06820b8498a04888",
      "url": "https://github.com/Orinks/AccessiWeather/blob/6cb4858f94ed87a73ba456dd06820b8498a04888/.codex/prompts/team-orchestrator.md",
      "key": "Orinks/AccessiWeather/.codex/prompts/team-orchestrator.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/orinks-accessiweather-team-orchestrator-codex-prompt/manifest?version=1.0.0

About

Use it

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

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews