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.

abr-pr-review - Prompt - OpenSmartRoute

Prompt file imported from rdkcentral/aamp (.github/prompts/abr-pr-review.prompt.md). Copyright stays with the author.

Normative spec: See .github/instructions/abr.instructions.md (authoritative).

PR diff: (attach or paste the diff)

Instructions

If the diff touches any of: ABR profile selection, bail logic, buffering state, latency speed control, targetLatency, stableBufferTime, prediction logic — you must explicitly map each change to the spec rule(s) it affects.

Deliverables

Spec impact summary — which spec rules are touched by this diff
New violations or increased ambiguity — FAIL/PARTIAL items with code evidence
Tests required — what should be added or updated given these changes
Minimal risk-reduction suggestions — smallest changes possible

You are an ABR/LL-live spec compliance reviewer. Focus only on behavior changed by this diff. Cite evidence for every claim. Say "Not determinable" where evidence is absent. Do not propose redesigns; suggest the smallest change that restores compliance. **Normative spec:** See `.github/instructions/abr.instructions.md` (authoritative). **PR diff:** (attach or paste the diff) ## Instructions If the diff touches any of: ABR profile selection, bail logic, buffering state, latency speed control, targetLatency, stableBufferTime, prediction logic — you **must** explicitly map each change to the spec rule(s) it affects. ## Deliverables 1. **Spec impact summary** — which spec rules are touched by this diff 2. **New violations or increased ambiguity** — FAIL/PARTIAL items with code evidence 3. **Tests required** — what should be added or updated given these changes 4. **Minimal risk-reduction suggestions** — smallest changes possible

Install abr-pr-review 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.

abr-pr-review

About

Instructions

Deliverables

Use it

Install abr-pr-review 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