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.

arsenalmed - Skill - OpenSmartRoute

Name: arsenalmed
Author: medneeds

Imported from medneeds/arsenalmed (AGENTS.md). Install upstream with npx skills add medneeds/arsenalmed. Copyright stays with the author.

[!IMPORTANT] This project is connected to Lovable. Avoid rewriting published git history — force pushing, or rebasing/amending/squashing commits that are already pushed — as it rewrites history on Lovable's side and the user will likely lose their project history.

Commits you push to the connected branch sync back to Lovable and show up in the editor, so keep the branch in a working state.

Rules

MedStation annual-plan bonus enters via POST /api/public/medstation-bonus: the reference is confirmed against MedStation's public verify endpoint (no shared secret), stored in compras with origem = 'medstation_bonus', valor_centavos = 0, stripe_session_id = 'medstation:' + reference; renewals only extend expira_em. Why: auditability without sharing secrets between projects.
Bonus rows are not sales: admin revenue, ticket and funnel metrics exclude origem = 'medstation_bonus'. Why: zero-value rows would distort sales figures.
Personalized PDFs are never generated at bonus registration; they are generated on first download and require a valid CPF on the purchase (collected at "Criar acesso" when missing). Why: delivery must always carry the buyer's identification.
Pure business rules live in small modules with vitest tests (bunx vitest run, config in vitest.config.ts). Why: the app's Vite config is not suitable for tests.

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

{ "ocm": "1", "id": "medneeds-arsenalmed-arsenalmed", "kind": "skill", "name": "arsenalmed", "description": " > [!IMPORTANT] > This project is connected to [Lovable](https://lovable.dev). Avoid rewriting > published git history — force pushing, or rebasing/amending/squashing commits > that are already pushed — as it rewrites history on Lovable's side and the > user will likely lose their project history. > > Commits you push to the connected branch sync back to Lovable and show up in > the editor, so keep the branch in a working state. ", "publisher": "medneeds", "version": "1.0.0", "capabilities": { "domains": [ "coding", "customer_support" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ " > [!IMPORTANT] > This project is connected to [Lovable](https://lovable.dev). Avoid rewriting > published git history — force pushing, or rebasing/amending/squashing commits > that are already pushed — as it rewrites history on Lovable's side and the > user will likely lose their project history. > > Commits you push to the connected branch sync back to Lovable and show up in > the editor, so keep the branch in a working state. " ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/medneeds/arsenalmed", "path": "AGENTS.md", "ref": "a0753780164661d70efd2ce0dd8cc1168397eb69", "url": "https://github.com/medneeds/arsenalmed/blob/a0753780164661d70efd2ce0dd8cc1168397eb69/AGENTS.md", "key": "medneeds/arsenalmed/AGENTS.md" } }, "instructions": "\n> [!IMPORTANT]\n> This project is connected to [Lovable](https://lovable.dev). Avoid rewriting\n> published git history — force pushing, or rebasing/amending/squashing commits\n> that are already pushed — as it rewrites history on Lovable's side and the\n> user will likely lose their project history.\n>\n> Commits you push to the connected branch sync back to Lovable and show up in\n> the editor, so keep the branch in a working state.\n\n\n## Rules\n- MedStation annual-plan bonus enters via POST /api/public/medstation-bonus: the reference is confirmed against Me", "cost": { "context_tokens": 360 } }

arsenalmed

About

Rules

Use it

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