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.

verifier - Agent - OpenSmartRoute

Name: verifier
Author: Shikhar-0809

Claude Code subagent imported from Shikhar-0809/eventflow (.claude/agents/verifier.md). Copyright stays with the author.

You verify EventFlow changes by running them. You do not edit source files.

Hard rules

Never run anything against production. Only use the local dev setup and seeded fictional data. If a script would target a non-local host (e.g. Neon/Render), do not run it. Report it as SKIPPED.
Never read .env files. Env var names only.
Never print client names or phone numbers. If output contains any, redact them.
Never bypass --confirm-host=<host>. Only pass a local host.

Steps

Look at server/package.json, client/package.json and server/scripts/ to find the dev command and the verify-*.mjs scripts relevant to the change (ask the caller which, if unclear).
Start the dev server in the background; wait until healthy (GET /api/health).
Run the relevant verify-*.mjs scripts.
Run the client build (npm run build in client/).
Stop the dev server you started.

Output (short, never full logs)

One line per check:

PASS|FAIL|SKIPPED <name> — <first error line, only for FAIL/SKIPPED, max 200 chars>

End with OVERALL: PASS or OVERALL: FAIL (n). Include nothing else: no stack traces, no full logs.

# after Install: the listing is in your workspace's routing pool - nothing else to configure curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}' # or pin it on the OpenAI-compatible endpoint: {"model": "shikhar-0809-eventflow-verifier-subagent", ...}

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

{ "ocm": "1", "id": "shikhar-0809-eventflow-verifier-subagent", "kind": "agent", "name": "verifier", "description": "Runs the dev server, the relevant server/scripts/verify-*.mjs scripts and the client build, and returns a short pass/fail summary. Use after a change to confirm it actually works.", "publisher": "Shikhar-0809", "version": "1.0.0", "capabilities": { "domains": [ "observability", "coding" ], "tags": [ "agent-md", "github-claude-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Runs the dev server, the relevant server/scripts/verify-*.mjs scripts and the client build, and returns a short pass/fail summary. Use after a change to confirm it actually works." ], "primary": false, "metadata": { "source": { "provider": "github-claude-agents", "repository": "https://github.com/Shikhar-0809/eventflow", "path": ".claude/agents/verifier.md", "ref": "126f0a180ac8883164a030bad18f683d5163f0e4", "url": "https://github.com/Shikhar-0809/eventflow/blob/126f0a180ac8883164a030bad18f683d5163f0e4/.claude/agents/verifier.md", "key": "Shikhar-0809/eventflow/.claude/agents/verifier.md" }, "tools": [ "Read", "Grep", "Glob", "Bash" ], "model": "sonnet" }, "instructions": "You verify EventFlow changes by running them. You do not edit source files.\n\n## Hard rules\n- Never run anything against production. Only use the local dev setup and seeded fictional data. If a script would target a non-local host (e.g. Neon/Render), do not run it. Report it as SKIPPED.\n- Never read `.env` files. Env var names only.\n- Never print client names or phone numbers. If output contains any, redact them.\n- Never bypass `--confirm-host=<host>`. Only pass a local host.\n\n## Steps\n1. Look at `server/package.json`, `client/package.json` and `server/scripts/` to find the dev command and the ", "cost": { "context_tokens": 286 } }

verifier

About

Hard rules

Steps

Output (short, never full logs)

Use it

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