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.

frontend - Skill - OpenSmartRoute

Instruction file imported from localtaskrepo/lotar (.github/instructions/frontend.instructions.md). Copyright stays with the author.

Frontend instructions (LoTaR)

Tech + UI conventions

Vue 3 + TypeScript + Vite.
Use Composition API with <script setup lang="ts">.
Prefer existing UI components in view/components/ (notably the Ui* components) and the local class-naming conventions.

API connectivity

Use the existing API client: view/api/client.ts.
Use the shared DTOs: view/api/types.ts (kept aligned with src/api_types.rs).
Prefer same-origin /api/* URLs (the Rust server serves both the SPA and the API).

Tests + lint

Typecheck frontend: npm run lint:frontend; lint: npm run lint:js; format: npm run fmt:js (Prettier).
Multi-statement inline handlers must be arrow functions (@click="() => { a(); b() }"): Prettier drops semicolons, and Vue cannot split statements without them.
UI unit tests: npm run test:ui (see the testing-strategy skill for targeting).

Change discipline

Stay within the task's scope; don't refactor unrelated UI.
If changing UX/behavior, add/update Vitest coverage where it fits, and verify visually (Playwright smoke / vision tools — see review-handoff) rather than eyeballing.

# 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 frontend 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.

frontend

About

Frontend instructions (LoTaR)

Tech + UI conventions

API connectivity

Tests + lint

Change discipline

Use it

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