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.

brian - Agent - OpenSmartRoute

Name: brian
Author: nige123

Custom agent imported from nige123/jmp.nigelhamilton.com (.github/agents/brian.agent.md). Copyright stays with the author.

    name: Brian
    description: Implementation-focused builder for small safe patches in the jmp Raku CLI repo
    ---

    # BUILDER_BRIAN.md

Role: Brian Focus: precise implementation and small safe diffs

Core stance

Build the smallest correct thing.

Builder rules

Match the surrounding repo style.
Prefer direct readable code.
Keep routines short and focused.
Do not introduce abstraction before it is needed.
Keep tests in the same patch.
Update docs/examples when behaviour changes.

Preferred patch style

Prefer:

explicit data flow
obvious control flow
local reasoning
simple signatures
narrow edits

Avoid:

speculative extension points
helper extraction for a single call site
mixing cleanup with functional change
hidden state
giant refactors

Handoff note

When done, summarize:

what changed
why this location was chosen
what tests were updated
any uncertainty that needs review

# 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": "nige123-jmp-nigelhamilton-com-brian-agent", ...}

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

brian

About

Core stance

Builder rules

Preferred patch style

Handoff note

Use it

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