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.

verify-e2e - Prompt - OpenSmartRoute

Name: verify-e2e
Author: carteracredit

Prompt file imported from carteracredit/forms (.cursor/commands/verify-e2e.md). Copyright stays with the author.

Verify e2e

Runbook for /verify-e2e after a user-visible or cross-service change.

Resolve the area

Read e2e/COVERAGE.md (workspace) or this repo's Identity E2E areas.
Pick the matching @area tag (@auth, @cases, @contractor, @admin, @forms, @workflow, @widgets, @chat, @calendar, @documents, @notifications, @prequalification, @promotions, @signatures).
Note the tier: prod-safe / cheap / dev-only.

Environment matrix

Env	When	Command
Preview (ADR 0011)	PR into `dev` is open — preferred for UI/journey on the unmerged SHA	`cd e2e && pnpm test:preview --slug <slug>`
Prod cheap	No open preview, or after the change is on prod	`cd e2e && pnpm test:prod:verify --grep @<area>`
Prod smoke only	No password secrets	`cd e2e && pnpm test:prod`
Dev	Deployed `*.carteracredit.workers.dev`	`cd e2e && pnpm test:dev --grep @<area>`
Local	`pnpm --dir harness dev` up	`cd e2e && E2E_ENV=local pnpm test --grep @<area>`

When a PR into dev is open, wait for the  comment (/healthz ok). Sign in on https://<slug>-auth.carteracredit.workers.dev/login with Cursor Cloud password secrets (clean browser profile — cookies share .carteracredit.workers.dev with stable-dev). Passkeys / Google / OTP do not work on preview aliases. Prod cheap cannot validate the unmerged branch.

Interpret results

Green — verification passed. Task may be marked done.
Skipped (allowWrites / env.name === "prod") — expected for onboarding writes on prod. Do not invent a prod write for those. If the task needed that journey, add or keep a required-missing COVERAGE.md row.
Red — not done. Fix the product or the spec, or report the failure.
No spec — add a spec or a required-missing row in the same task.

Hands and eyes

cd e2e
pnpm snap customer /cases
pnpm snap operator https://admin.carteracredit.workers.dev
pnpm snap guest https://auth.carteracredit.workers.dev/login
pnpm probe GET /healthz

Never toggle persona password-login. Never read prod KV.

Install verify-e2e 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.

# Verify e2e Runbook for `/verify-e2e` after a user-visible or cross-service change. ## Resolve the area 1. Read `e2e/COVERAGE.md` (workspace) or this repo's Identity **E2E areas**. 2. Pick the matching `@area` tag (`@auth`, `@cases`, `@contractor`, `@admin`, `@forms`, `@workflow`, `@widgets`, `@chat`, `@calendar`, `@documents`, `@notifications`, `@prequalification`, `@promotions`, `@signatures`). 3. Note the tier: `prod-safe` / `cheap` / `dev-only`. ## Environment matrix | Env | When | Command | | ------------------ | -------------------------------------------------------------------- | -------------------------------------------------- | | Preview (ADR 0011) | PR into `dev` is open — preferred for UI/journey on the unmerged SHA | `cd e2e && pnpm test:preview --slug <slug>` | | Prod cheap | No open preview, or after the change is on prod | `cd e2e && pnpm test:prod:verify --grep @<area>` | | Prod smoke only | No password secrets | `cd e2e && pnpm test:prod` | | Dev | Deployed `*.carteracredit.workers.dev` | `cd e2e && pnpm test:dev --grep @<area>` | | Local | `pnpm --dir harness dev` up | `cd e2e && E2E_ENV=local pnpm test --grep @<area>` | When a PR into `dev` is open, wait for the `` comment (`/healthz` ok). Sign in on `https://<slug>-auth.carteracredit.workers.dev/login` with Cursor Cloud password secrets (clean browser profile — cookies share `.carteracredit.workers.dev` with stable-dev). Passkeys / Google / OTP do not work on preview aliases. Prod cheap cannot validate the unmerged branch. ## Interpret results - **Green** — verification passed. Task may be marked done. - **Skipped (`allowWrites` / `env.name === "prod"`)** — expected for onboarding writes on prod. Do not invent a prod write for those. If the task needed that journey, add or keep a `required-missing` COVERAGE.md row. - **Red** — not done. Fix the product or the spec, or report the failure. - **No spec** — add a spec or a `required-missing` row in the same task. ## Hands and eyes ```bash cd e2e pnpm snap customer /cases pnpm snap operator https://admin.carteracredit.workers.dev pnpm snap guest https://auth.carteracredit.workers.dev/login pnpm probe GET /healthz ``` Never toggle persona password-login. Never read prod KV.

{ "prompt": "# Verify e2e\n\nRunbook for `/verify-e2e` after a user-visible or cross-service change.\n\n## Resolve the area\n\n1. Read `e2e/COVERAGE.md` (workspace) or this repo's Identity **E2E areas**.\n2. Pick the matching `@area` tag (`@auth`, `@cases`, `@contractor`, `@admin`,\n `@forms`, `@workflow`, `@widgets`, `@chat`, `@calendar`, `@documents`,\n `@notifications`, `@prequalification`, `@promotions`, `@signatures`).\n3. Note the tier: `prod-safe` / `cheap` / `dev-only`.\n\n## Environment matrix\n\n| Env | When | Command |\n| ------------------ | -------------------------------------------------------------------- | -------------------------------------------------- |\n| Preview (ADR 0011) | PR into `dev` is open — preferred for UI/journey on the unmerged SHA | `cd e2e && pnpm test:preview --slug <slug>` |\n| Prod cheap | No open preview, or after the change is on prod | `cd e2e && pnpm test:prod:verify --grep @<area>` |\n| Prod smoke only | No password secrets | `cd e2e && pnpm test:prod` |\n| Dev | Deployed `*.carteracredit.workers.dev` | `cd e2e && pnpm test:dev --grep @<area>` |\n| Local | `pnpm --dir harness dev` up | `cd e2e && E2E_ENV=local pnpm test --grep @<area>` |\n\nWhen a PR into `dev` is open, wait for the ``\ncomment (`/healthz` ok). Sign in on\n`https://<slug>-auth.carteracredit.workers.dev/login` with Cursor Cloud\npassword secrets (clean browser profile — cookies share\n`.carteracredit.workers.dev` with stable-dev). Passkeys / Google / OTP do\nnot work on preview aliases. Prod cheap cannot validate the unmerged branch.\n\n## Interpret results\n\n- **Green** — verification passed. Task may be marked done.\n- **Skipped (`allowWrites` / `env.name === \"prod\"`)** — expected for\n onboarding writes on prod. Do not invent a prod write for those. If the\n task needed that journey, add or keep a `required-missing` COVERAGE.md row.\n- **Red** — not done. Fix the product or the spec, or report the failure.\n- **No spec** — add a spec or a `required-missing` row in the same task.\n\n## Hands and eyes\n\n```bash\ncd e2e\npnpm snap customer /cases\npnpm snap operator https://admin.carteracredit.workers.dev\npnpm snap guest https://auth.carteracredit.workers.dev/login\npnpm probe GET /healthz\n```\n\nNever toggle persona password-login. Never read prod KV.", "variables": [], "notes": "Runbook for `/verify-e2e` after a user-visible or cross-service change.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/carteracredit/forms", "path": ".cursor/commands/verify-e2e.md", "ref": "4065f1f018e01b8758a3ed2298b8f6b215ce36d5", "url": "https://github.com/carteracredit/forms/blob/4065f1f018e01b8758a3ed2298b8f6b215ce36d5/.cursor/commands/verify-e2e.md", "key": "carteracredit/forms/.cursor/commands/verify-e2e.md" } } }

verify-e2e

About

Verify e2e

Resolve the area

Environment matrix

Interpret results

Hands and eyes

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