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.

code-review - Prompt - OpenSmartRoute

Name: code-review
Author: reuben2crown

Prompt file imported from reuben2crown/disclo (.cursor/commands/code-review.md). Copyright stays with the author.

Review the changes on @branch:

Think through how data flows in the app. Explain new patterns if they exist and why.
Were there any changes that could affect infrastructure?
Consider empty, loading, error, and offline states.
Review frontend changes for a11y (keyboard navigation, focus management, ARIA roles, color contrast).
If public APIs have changed, ensure backwards compat (or increment API version).
Did we add any unnecessary dependencies? If there's a heavy dependency, could we inline a more minimal version?
Did we add quality tests? Prefer fewer, high quality tests. Prefer integration tests for user flows.
Were there schema changes which could require a database migration?
Changes to auth flows or permissions? Run /security-review.
If feature flags are set up, does this change require adding a new one?
Are there places we should use caching?
Are we missing critical o11y or logging on backend changes?

Disclo-specific checks

Is packages/core free of imports from packages/adapters?
Do all new adapter files implement only the PlatformAdapter interface methods?
Is plan enforcement middleware applied before business logic on all new premium routes?
Are OAuth tokens and API keys encrypted via packages/core/src/crypto.ts?
Are all inbound webhook signatures verified before processing?
Does process.env appear only in packages/core/src/config.ts?
Are all external API calls (GPTZero, Hive, Anthropic, Stripe) wrapped in typed error classes?
Are tests written before implementation (TDD)? Check commit history.
Are there any test.skip or it.skip in the new test files?
Does the audit log record all new compliance actions?
For Green Claims changes: is there a consumer-visible badge, or is it correctly merchant-facing only?

Install code-review 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": "Review the changes on @branch:\n\n- Think through how data flows in the app. Explain new patterns if they exist and why.\n- Were there any changes that could affect infrastructure?\n- Consider empty, loading, error, and offline states.\n- Review frontend changes for a11y (keyboard navigation, focus management, ARIA roles, color contrast).\n- If public APIs have changed, ensure backwards compat (or increment API version).\n- Did we add any unnecessary dependencies? If there's a heavy dependency, could we inline a more minimal version?\n- Did we add quality tests? Prefer fewer, high quality tests. Prefer integration tests for user flows.\n- Were there schema changes which could require a database migration?\n- Changes to auth flows or permissions? Run /security-review.\n- If feature flags are set up, does this change require adding a new one?\n- Are there places we should use caching?\n- Are we missing critical o11y or logging on backend changes?\n\n## Disclo-specific checks\n\n- Is `packages/core` free of imports from `packages/adapters`?\n- Do all new adapter files implement only the `PlatformAdapter` interface methods?\n- Is plan enforcement middleware applied before business logic on all new premium routes?\n- Are OAuth tokens and API keys encrypted via `packages/core/src/crypto.ts`?\n- Are all inbound webhook signatures verified before processing?\n- Does `process.env` appear only in `packages/core/src/config.ts`?\n- Are all external API calls (GPTZero, Hive, Anthropic, Stripe) wrapped in typed error classes?\n- Are tests written before implementation (TDD)? Check commit history.\n- Are there any `test.skip` or `it.skip` in the new test files?\n- Does the audit log record all new compliance actions?\n- For Green Claims changes: is there a consumer-visible badge, or is it correctly merchant-facing only?", "variables": [], "notes": "Review the changes on @branch:", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/reuben2crown/disclo", "path": ".cursor/commands/code-review.md", "ref": "bf8e3f6ff2d14dc1a00705ad6d4fb7d26624612d", "url": "https://github.com/reuben2crown/disclo/blob/bf8e3f6ff2d14dc1a00705ad6d4fb7d26624612d/.cursor/commands/code-review.md", "key": "reuben2crown/disclo/.cursor/commands/code-review.md" } } }

code-review

About

Disclo-specific checks

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

Use it

Manifest

Reviews