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.

90 days of the enterprise, pro and team plans free, no card needed. See the plans

OpenSmartRoute

saans - Prompt - OpenSmartRoute

Promptv1.0.0

saans

Name: saans
Author: RaghavK16

Run Saans (collect + brief) and reply with today's 5-line plan

by RaghavK16(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Prompt file imported from RaghavK16/saans (.claude/commands/saans.md). Fill in {{arguments}} before use. Copyright stays with the author.

Run the Saans CLI from the project root and report back.

Run .venv/bin/saans {{arguments}}. If no arguments were given, run .venv/bin/saans run. It takes about a minute (a backfill takes longer). Don't fetch anything else yourself.
Show the per-source status lines it printed (ok / skipped / failed) in one short list. Call out any failed source with its detail. A skipped datagovin just means the key isn't set.
If the command wrote a brief, open the newest out/brief-*.md and reply with:
- the bullet lines under "## Today's plan" exactly as written (the 5-line summary),
- any "⚠" note at the top of the brief (e.g. missed days),
- the path to the HTML brief so it can be opened.
Keep it short. Don't restate the reasons sections unless asked; don't edit any files.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

Run the Saans CLI from the project root and report back.

1. Run `.venv/bin/saans {{arguments}}`. If no arguments were given, run `.venv/bin/saans run`.
   It takes about a minute (a backfill takes longer). Don't fetch anything else yourself.
2. Show the per-source status lines it printed (ok / skipped / failed) in one short list.
   Call out any **failed** source with its detail. A skipped `datagovin` just means the key isn't set.
3. If the command wrote a brief, open the newest `out/brief-*.md` and reply with:
   - the bullet lines under "## Today's plan" exactly as written (the 5-line summary),
   - any "⚠" note at the top of the brief (e.g. missed days),
   - the path to the HTML brief so it can be opened.
4. Keep it short. Don't restate the reasons sections unless asked; don't edit any files.

Installed into a catalogue, chosen by a router

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

Photo: RDNE Stock project

For the business

What it costs to adopt - in engineering time.

Same client, same code
One base URL
The OpenAI-compatible endpoint answers your existing SDK calls; model=auto lets the router choose.
The SDKs
One URL, every vendor
No vendor lock-in
Point your OpenAI-compatible client at one address; add, swap or retire providers in the catalogue without touching application code.
Every vendor side by side
Next eligible model answers
Failover built in
When a provider is down or over quota the request moves on; the trace says it did.

Manifest

The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.

raghavk16-saans-saans-command.prompt.jsonjson

{
  "prompt": "Run the Saans CLI from the project root and report back.\n\n1. Run `.venv/bin/saans {{arguments}}`. If no arguments were given, run `.venv/bin/saans run`.\n   It takes about a minute (a backfill takes longer). Don't fetch anything else yourself.\n2. Show the per-source status lines it printed (ok / skipped / failed) in one short list.\n   Call out any **failed** source with its detail. A skipped `datagovin` just means the key isn't set.\n3. If the command wrote a brief, open the newest `out/brief-*.md` and reply with:\n   - the bullet lines under \"## Today's plan\" exactly as written (the 5-line summary),\n   - any \"⚠\" note at the top of the brief (e.g. missed days),\n   - the path to the HTML brief so it can be opened.\n4. Keep it short. Don't restate the reasons sections unless asked; don't edit any files.",
  "variables": [
    "arguments"
  ],
  "notes": "Run Saans (collect + brief) and reply with today's 5-line plan Tools: Bash(.venv/bin/saans:*), Bash(ls:*), Read. Arguments: [run|brief|collect|backfill cpcb_bulletin|reparse]  (default: run).",
  "metadata": {
    "source": {
      "provider": "github-claude-commands",
      "repository": "https://github.com/RaghavK16/saans",
      "path": ".claude/commands/saans.md",
      "ref": "8328383c242a76bcd0fda870de06b603e122cda6",
      "url": "https://github.com/RaghavK16/saans/blob/8328383c242a76bcd0fda870de06b603e122cda6/.claude/commands/saans.md",
      "key": "RaghavK16/saans/.claude/commands/saans.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/raghavk16-saans-saans-command/manifest?version=1.0.0

About

Use it

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