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.

dashboard - Skill - OpenSmartRoute

Imported from BelimbingApp/bilibi (apps/base/dashboard/AGENTS.md). Install upstream with npx skills add BelimbingApp/bilibi --skill dashboard. Copyright stays with the author.

Dashboard agent notes

Contribute an entry with bilibi_dashboard::contribute! plus an Embed whose context is EmbedContext::Dashboard, not a card or page of your own on /dashboard: the page mounts each entry as an independent server-declared panel, so permission loss, refresh and drag order work per entry; README.md is the contract and apps/web/examples/dashboard-reference.rs a runnable specimen.
A panel renders one root element whose id is PanelArgs::id() and reads through PanelCache, not on every update: the host refreshes every panel on every parent update and on its 15 s tick, so an uncached panel turns each Customize click into a read.
Never rename an entry id or rewrite the ui.dashboard.* keys: ids are stored in each account's arrangement.
The page keeps each panel in a keyed data-live-ignore slot (slot-<id>) inside a keyed wrapper; drop the keys or the ignore and a page patch blanks the panels until the next fragment.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot 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}'

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

dashboard

About

Dashboard agent notes

Use it

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