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.

review-changes - Prompt - OpenSmartRoute

Prompt file imported from nadir511/PlcTelegramSimulator (.github/prompts/review-changes.prompt.md). Copyright stays with the author.

Goal

Perform a high-signal review of the current change set (or the scope/PR in the argument).

Steps

Read the diff, the plan (if any), and relevant ADRs; understand the intent first.
Trace the critical paths:
- Backend — telegram framing/encoding, transport lifecycle, CancellationToken on I/O, API contract, error handling, layer boundaries (Web/Infrastructure → Application → Domain).
- Frontend — data flow, live-stream subscribe/cleanup, typed API usage, loading/error states.
Check security: no secrets committed or logged, external input validated, no unsafe deserialization.
Confirm tests exist for the behavior changed and actually exercise it.
Report findings by severity (blocking / warning / info) with file:line evidence and your confidence. Skip nits already handled by dotnet format / ESLint. Missing tests for a behavior change = blocking.

# Goal Perform a high-signal review of the current change set (or the scope/PR in the argument). ## Steps 1. Read the diff, the plan (if any), and relevant ADRs; understand the intent first. 2. Trace the critical paths: - **Backend** — telegram framing/encoding, transport lifecycle, `CancellationToken` on I/O, API contract, error handling, layer boundaries (`Web`/`Infrastructure` → `Application` → `Domain`). - **Frontend** — data flow, live-stream subscribe/cleanup, typed API usage, loading/error states. 3. Check security: no secrets committed or logged, external input validated, no unsafe deserialization. 4. Confirm tests exist for the behavior changed and actually exercise it. 5. Report findings by severity (**blocking / warning / info**) with file:line evidence and your confidence. Skip nits already handled by `dotnet format` / ESLint. Missing tests for a behavior change = blocking.

Install review-changes 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.

review-changes

About

Goal

Steps

Use it

Install review-changes 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