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.

09-verify - Prompt - OpenSmartRoute

Name: 09-verify
Author: esmaeilzadeh

Prompt file imported from esmaeilzadeh/agent-starter-kit (.cursor/commands/09-verify.md). Copyright stays with the author.

Generated by sync-cursor-binding.sh — do not hand-edit; edit .agents/ask/stages instead.

Kit Protocol: 09 Verify

Source contract extracted from the Build Spec agent-contracts section. Portable SoT for this stage.

Evidence via ./ask verify (fail-closed CheckPlan) and _ask/templates/verification.json.

15.9 09 Verify Agent

Purpose:

Produce evidence appropriate to the changed system and risk class.

Run ./ask verify. The committed CheckPlan is .agents/verification.yaml. Empty CheckPlan or zero mandatory checks fails closed. Logic lives in .agents/ask/verification/. Language CLIs live in presets, not in this contract and not in _ask/scripts/verify.sh.

Do not overlay ./ask verify with npm, pytest, cargo, or any other language CLI.

It must record the exact commit SHA.

Kit path

See _ask/policies/workflow.md. Claiming verify without running ./ask verify or a commit SHA stays hard. Prepare verification evidence; Accept is the human close.

E2E

Run confirmed E2E checks from .agents/verification.yaml unless e2e: not_applicable plus reason. Record the commit SHA.

Structured test evidence

./ask verify composes static checks and actual per-case execution through the shared Python completion gate; retain its candidate SHA and per-criterion completion report.

Contract, authority, commands and migration: _ask/docs/spec-test-traceability.md.

Install 09-verify 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": "# Generated by sync-cursor-binding.sh — do not hand-edit; edit .agents/ask/stages instead.\n\n# Kit Protocol: 09 Verify\n\nSource contract extracted from the Build Spec agent-contracts section. Portable SoT for this stage.\n\nEvidence via `./ask verify` (fail-closed CheckPlan) and `_ask/templates/verification.json`.\n\n## 15.9 09 Verify Agent\n\nPurpose:\n\n```text\nProduce evidence appropriate to the changed system and risk class.\n```\n\nRun `./ask verify`. The committed CheckPlan is `.agents/verification.yaml`.\nEmpty CheckPlan or zero mandatory checks fails closed. Logic lives in\n`.agents/ask/verification/`. Language CLIs live in presets, not in this\ncontract and not in `_ask/scripts/verify.sh`.\n\nDo not overlay `./ask verify` with npm, pytest, cargo, or any other language\nCLI.\n\nIt must record the exact commit SHA.\n\n---\n\n## Kit path\n\nSee `_ask/policies/workflow.md`. Claiming verify without running `./ask verify`\nor a commit SHA stays **hard**. Prepare verification evidence; Accept is the\nhuman close.\n\n## E2E\n\nRun confirmed E2E checks from `.agents/verification.yaml` unless\n`e2e: not_applicable` plus reason. Record the commit SHA.\n\n## Structured test evidence\n\n`./ask verify` composes static checks and actual per-case execution through the shared Python completion gate; retain its candidate SHA and per-criterion completion report.\n\nContract, authority, commands and migration: `_ask/docs/spec-test-traceability.md`.", "variables": [], "notes": "Source contract extracted from the Build Spec agent-contracts section. Portable SoT for this stage.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/esmaeilzadeh/agent-starter-kit", "path": ".cursor/commands/09-verify.md", "ref": "4a1967a3c8586f5dcfde979b5f4449d4df2dd3ff", "url": "https://github.com/esmaeilzadeh/agent-starter-kit/blob/4a1967a3c8586f5dcfde979b5f4449d4df2dd3ff/.cursor/commands/09-verify.md", "key": "esmaeilzadeh/agent-starter-kit/.cursor/commands/09-verify.md" } } }

09-verify

About

Generated by sync-cursor-binding.sh — do not hand-edit; edit .agents/ask/stages instead.

Kit Protocol: 09 Verify

15.9 09 Verify Agent

Kit path

E2E

Structured test evidence

Use it

Install 09-verify 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