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.

clarify - Prompt - OpenSmartRoute

Prompt file imported from ManjiDM/FairBets (.github/prompts/clarify.prompt.md). Fill in {{spec}} before use. Copyright stays with the author.

Clarify

Resolve the open questions in specs/{{spec}}/spec.md.

Steps

Read the spec and collect every [NEEDS CLARIFICATION: ...] marker.
Rank them by impact. Anything affecting money rules, persisted data shapes, or risk limits comes first.
Ask the user, one focused batch at a time, offering a concrete recommended default for each question so answering is cheap.
Write each answer into the relevant spec section and delete the marker.
Re-check the acceptance scenarios: an answer usually changes or adds one.

Rules

Never resolve a money, data-shape, or risk-limit question by guessing.
Questions you can answer yourself from the codebase are not clarifications — answer them from src/domain/ledger.ts, src/lib/cloudStore.ts, or e2e/features/ and record the finding.
The spec must contain zero markers before planning starts.
If an answer contradicts ../../specs/constitution.md, raise it explicitly instead of proceeding.

Output

List each question, the answer applied, and confirm the spec now has no remaining [NEEDS CLARIFICATION] markers.

# Clarify Resolve the open questions in `specs/{{spec}}/spec.md`. ## Steps 1. Read the spec and collect every `[NEEDS CLARIFICATION: ...]` marker. 2. Rank them by impact. Anything affecting money rules, persisted data shapes, or risk limits comes first. 3. Ask the user, one focused batch at a time, offering a concrete recommended default for each question so answering is cheap. 4. Write each answer into the relevant spec section and delete the marker. 5. Re-check the acceptance scenarios: an answer usually changes or adds one. ## Rules - Never resolve a money, data-shape, or risk-limit question by guessing. - Questions you can answer yourself from the codebase are not clarifications — answer them from `src/domain/ledger.ts`, `src/lib/cloudStore.ts`, or `e2e/features/` and record the finding. - The spec must contain zero markers before planning starts. - If an answer contradicts [`../../specs/constitution.md`](../../specs/constitution.md), raise it explicitly instead of proceeding. ## Output List each question, the answer applied, and confirm the spec now has no remaining `[NEEDS CLARIFICATION]` markers.

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

clarify

About

Clarify

Steps

Rules

Output

Use it

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