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.

90 days of the enterprise, pro and team plans free, no card needed. See the plans

OpenSmartRoute

mvvm-compliance-review - Prompt - OpenSmartRoute

Promptv1.0.0

mvvm-compliance-review

Name: mvvm-compliance-review
Author: rodoHasArrived

Objective: review a Meridian desktop area for MVVM boundary violations and practical refactoring steps.

by rodoHasArrived(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Prompt file imported from rodoHasArrived/Meridian-main (.codex/prompts/mvvm-compliance-review.md). Copyright stays with the author.

Review MVVM Compliance

Objective: review a Meridian desktop area for MVVM boundary violations and practical refactoring steps.

Constraints:

Inventory views, code-behind, view models, services, commands, and tests first.
Separate verified findings from inferred risks.
Prioritize business logic in views, provider calls from UI, missing command state, missing loading/error/empty states, and untestable workflow logic.
Include resource risks such as sync I/O, blocking waits, unbounded collections, and polling.
Recommend the smallest safe sequence of fixes.

Final summary must include findings, file references, suggested tests, and refactor order.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

# Review MVVM Compliance

Objective: review a Meridian desktop area for MVVM boundary violations and practical refactoring
steps.

Constraints:
- Inventory views, code-behind, view models, services, commands, and tests first.
- Separate verified findings from inferred risks.
- Prioritize business logic in views, provider calls from UI, missing command state, missing
  loading/error/empty states, and untestable workflow logic.
- Include resource risks such as sync I/O, blocking waits, unbounded collections, and polling.
- Recommend the smallest safe sequence of fixes.

Final summary must include findings, file references, suggested tests, and refactor order.

Installed into a catalogue, chosen by a router

Install mvvm-compliance-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.

Photo: RDNE Stock project

For the business

What it costs to adopt - in engineering time.

Same client, same code
One base URL
The OpenAI-compatible endpoint answers your existing SDK calls; model=auto lets the router choose.
The SDKs
One URL, every vendor
No vendor lock-in
Point your OpenAI-compatible client at one address; add, swap or retire providers in the catalogue without touching application code.
Every vendor side by side
Next eligible model answers
Failover built in
When a provider is down or over quota the request moves on; the trace says it did.

Manifest

The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.

rodohasarrived-meridian-main-mvvm-compliance-review-code-bf79ea.prompt.jsonjson

{
  "prompt": "# Review MVVM Compliance\n\nObjective: review a Meridian desktop area for MVVM boundary violations and practical refactoring\nsteps.\n\nConstraints:\n- Inventory views, code-behind, view models, services, commands, and tests first.\n- Separate verified findings from inferred risks.\n- Prioritize business logic in views, provider calls from UI, missing command state, missing\n  loading/error/empty states, and untestable workflow logic.\n- Include resource risks such as sync I/O, blocking waits, unbounded collections, and polling.\n- Recommend the smallest safe sequence of fixes.\n\nFinal summary must include findings, file references, suggested tests, and refactor order.",
  "variables": [],
  "notes": "Objective: review a Meridian desktop area for MVVM boundary violations and practical refactoring steps.",
  "metadata": {
    "source": {
      "provider": "github-codex-prompts",
      "repository": "https://github.com/rodoHasArrived/Meridian-main",
      "path": ".codex/prompts/mvvm-compliance-review.md",
      "ref": "2ed48d5dbab48a3af0fefba61e8fe459c110f68a",
      "url": "https://github.com/rodoHasArrived/Meridian-main/blob/2ed48d5dbab48a3af0fefba61e8fe459c110f68a/.codex/prompts/mvvm-compliance-review.md",
      "key": "rodoHasArrived/Meridian-main/.codex/prompts/mvvm-compliance-review.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/rodohasarrived-meridian-main-mvvm-compliance-review-code-bf79ea/manifest?version=1.0.0

About

Review MVVM Compliance

Use it

Install mvvm-compliance-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