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.

health-check - Prompt - OpenSmartRoute

Prompt file imported from Oweeboi011/mms-open-climbs (.claude/commands/health-check.md). Copyright stays with the author.

Run a quick health check of the project's current state and surface anything that looks off.

Check the following in parallel and report findings:

Git state — uncommitted changes, untracked files, divergence of develop from origin/develop (a push to develop deploys)
CI — gh run list --limit 8: latest Firebase CI/CD, Supply chain & patterns, CodeQL, Create-Release and CSP watch results
Open PRs and issues — gh pr list, gh issue list (csp-watch files CSP violations as an issue)
Dependencies — npm run audit:deps (production deps, moderate+, frontend and functions)
Static gates — npm run quality (lint, layering, CSS collisions, duplication, dead code, secrets)
Env — .env exists, VITE_USE_FIREBASE_EMULATOR is what the user expects (not true means npm run dev hits production data)

Present results as a brief status board: green (ok), yellow (worth checking), red (action needed). One line per item.

Run a quick health check of the project's current state and surface anything that looks off. Check the following in parallel and report findings: 1. **Git state** — uncommitted changes, untracked files, divergence of `develop` from `origin/develop` (a push to `develop` deploys) 2. **CI** — `gh run list --limit 8`: latest Firebase CI/CD, Supply chain & patterns, CodeQL, Create-Release and CSP watch results 3. **Open PRs and issues** — `gh pr list`, `gh issue list` (csp-watch files CSP violations as an issue) 4. **Dependencies** — `npm run audit:deps` (production deps, moderate+, frontend and functions) 5. **Static gates** — `npm run quality` (lint, layering, CSS collisions, duplication, dead code, secrets) 6. **Env** — `.env` exists, `VITE_USE_FIREBASE_EMULATOR` is what the user expects (not `true` means `npm run dev` hits production data) Present results as a brief status board: green (ok), yellow (worth checking), red (action needed). One line per item.

Install health-check 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.

health-check

About

Use it

Install health-check 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