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.

spec - Prompt - OpenSmartRoute

Name: spec
Author: albegali

Prompt file imported from albegali/agentic-skeleton (.codex/prompts/spec.md). Fill in {{arguments}} before use. Copyright stays with the author.

Recommended model: gpt-5-codex (codex -p balanced) (tier balanced, see models.toml). Switch to it before running this command.

Developer mode. Arguments: {{arguments}}. Update only delivery/20-specs/SPEC-<ID>-*.md as requested, following delivery/templates/SPEC-template.md. The requests are the arguments plus the human's open requests in Spec §10 Notes / Clarifications: apply them all and mark each handled request in §10 (→ done <date>, or → not applied: <reason>). Do not touch the Brief, except for an Addendum (Brief §8) if the intent changes. If the RUN strategy is already approved (RUN §2) and the RUN is not Closed/Cancelled: set the Spec to Draft, add a RUN §6 Deviation #n (what changed in the Spec, plan impact, Scope impact: Requires approval) and set the RUN to Blocked. The human sets the Spec back to Ready, then runs /run <ID> approve-deviation <n>. Chat: 3 lines with what changed and, if the RUN was blocked, the two pending gates.

> Recommended model: **gpt-5-codex** (`codex -p balanced`) (tier `balanced`, see models.toml). Switch to it before running this command. Developer mode. Arguments: {{arguments}}. Update only `delivery/20-specs/SPEC-<ID>-*.md` as requested, following `delivery/templates/SPEC-template.md`. The requests are the arguments plus the human's open requests in Spec §10 Notes / Clarifications: apply them all and mark each handled request in §10 (`→ done <date>`, or `→ not applied: <reason>`). Do not touch the Brief, except for an Addendum (Brief §8) if the intent changes. If the RUN strategy is already approved (RUN §2) and the RUN is not Closed/Cancelled: set the Spec to `Draft`, add a RUN §6 `Deviation #n` (what changed in the Spec, plan impact, `Scope impact: Requires approval`) and set the RUN to `Blocked`. The human sets the Spec back to `Ready`, then runs `/run <ID> approve-deviation <n>`. Chat: 3 lines with what changed and, if the RUN was blocked, the two pending gates.

Install spec 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.

{ "prompt": "\n> Recommended model: **gpt-5-codex** (`codex -p balanced`) (tier `balanced`, see models.toml). Switch to it before running this command.\n\nDeveloper mode. Arguments: {{arguments}}. Update only `delivery/20-specs/SPEC-<ID>-*.md` as requested, following `delivery/templates/SPEC-template.md`.\nThe requests are the arguments plus the human's open requests in Spec §10 Notes / Clarifications: apply them all and mark each handled request in §10 (`→ done <date>`, or `→ not applied: <reason>`).\nDo not touch the Brief, except for an Addendum (Brief §8) if the intent changes.\nIf the RUN strategy is already approved (RUN §2) and the RUN is not Closed/Cancelled: set the Spec to `Draft`, add a RUN §6 `Deviation #n` (what changed in the Spec, plan impact, `Scope impact: Requires approval`) and set the RUN to `Blocked`. The human sets the Spec back to `Ready`, then runs `/run <ID> approve-deviation <n>`.\nChat: 3 lines with what changed and, if the RUN was blocked, the two pending gates.", "variables": [ "arguments" ], "notes": "Developer mode — update an existing Spec (e.g. after human review) Arguments: <ID> <requested changes>.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/albegali/agentic-skeleton", "path": ".codex/prompts/spec.md", "ref": "440cc31f5d6e30411e6f1db1861ee9530b52f192", "url": "https://github.com/albegali/agentic-skeleton/blob/440cc31f5d6e30411e6f1db1861ee9530b52f192/.codex/prompts/spec.md", "key": "albegali/agentic-skeleton/.codex/prompts/spec.md" } } }

spec

About

Use it

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