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.

proof-cli-baran - Skill - OpenSmartRoute

Imported from proof-computer/proof-cli-baran (AGENTS.md). Install upstream with npx skills add proof-computer/proof-cli-baran. Copyright stays with the author.

Agent Instructions

This public package owns the Switchboard plugin for the root proof CLI.

Keep this package public-safe. Do not add private Blackbox, Lockbox, Slipway, relay-ops, or monorepo-only dependencies.
This is the home for user-facing Switchboard CLI work. Add or change proof switchboard ... behavior here as native oclif commands.
Do not restore the generic compatibility bridge to the standalone switchboard binary. Command wrappers may call temporary command-specific shared runners while code is migrated, but missing runner exports must fail closed instead of spawning legacy non-oclif CLI code.
Keep public command names and flags stable unless a migration slice explicitly scopes the breaking change.
Keep package verification focused on the npm tarball surface: dist, oclif.manifest.json, and README.md.

CLI Development Guidance

When extracting native oclif commands or changing command behavior, review Liran Tal's Node.js CLI Apps Best Practices and its agent-oriented skill:

Use it as a checklist for POSIX-style flags, downstream help behavior, structured output, configuration precedence, actionable errors, debug output, exit codes, version output, package files, strict opt-in analytics, and argument-injection safety. The oclif plugin is the command contract; legacy standalone switchboard behavior is not a compatibility target to preserve unless a migration slice explicitly says so.

Install proof-cli-baran 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.

proof-cli-baran

About

Agent Instructions

CLI Development Guidance

Install proof-cli-baran 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