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

test - Prompt - OpenSmartRoute

Promptv1.0.0

test

Name: test
Author: BrianMF7

Run TDD workflow — write failing tests, implement, verify. For bugs, use the Prove-It pattern.

by BrianMF7(0) 0 installs

Free

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

See reviews

About

Prompt file imported from BrianMF7/HackNight (.cursor/commands/test.md). Copyright stays with the author.

Read and follow .cursor/skills/test-driven-development/SKILL.md.

Proof stays with this command. Ponytail may refuse only harness bloat: a new test dependency or a homemade framework when a small assert would do. It must not delete, skip, or weaken an assertion /build or /test added.

For new features:

Write tests that describe the expected behavior (they should FAIL)
Implement the code to make them pass
Refactor while keeping tests green

For bug fixes (Prove-It pattern):

Write a test that reproduces the bug (must FAIL)
Confirm the test fails
Implement the fix
Confirm the test passes
Run the full test suite for regressions

For browser-related issues, also follow .cursor/skills/browser-testing-with-devtools/SKILL.md to verify with the browser tools.

Use it

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

Read and follow `.cursor/skills/test-driven-development/SKILL.md`.

Proof stays with this command. Ponytail may refuse only harness bloat: a new test dependency or a homemade framework when a small assert would do. It must not delete, skip, or weaken an assertion `/build` or `/test` added.

For new features:
1. Write tests that describe the expected behavior (they should FAIL)
2. Implement the code to make them pass
3. Refactor while keeping tests green

For bug fixes (Prove-It pattern):
1. Write a test that reproduces the bug (must FAIL)
2. Confirm the test fails
3. Implement the fix
4. Confirm the test passes
5. Run the full test suite for regressions

For browser-related issues, also follow `.cursor/skills/browser-testing-with-devtools/SKILL.md` to verify with the browser tools.

Installed into a catalogue, chosen by a router

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

brianmf7-hacknight-test-cursor-command.prompt.jsonjson

{
  "prompt": "Read and follow `.cursor/skills/test-driven-development/SKILL.md`.\n\nProof stays with this command. Ponytail may refuse only harness bloat: a new test dependency or a homemade framework when a small assert would do. It must not delete, skip, or weaken an assertion `/build` or `/test` added.\n\nFor new features:\n1. Write tests that describe the expected behavior (they should FAIL)\n2. Implement the code to make them pass\n3. Refactor while keeping tests green\n\nFor bug fixes (Prove-It pattern):\n1. Write a test that reproduces the bug (must FAIL)\n2. Confirm the test fails\n3. Implement the fix\n4. Confirm the test passes\n5. Run the full test suite for regressions\n\nFor browser-related issues, also follow `.cursor/skills/browser-testing-with-devtools/SKILL.md` to verify with the browser tools.",
  "variables": [],
  "notes": "Run TDD workflow — write failing tests, implement, verify. For bugs, use the Prove-It pattern.",
  "metadata": {
    "source": {
      "provider": "github-cursor-commands",
      "repository": "https://github.com/BrianMF7/HackNight",
      "path": ".cursor/commands/test.md",
      "ref": "95e25cd4ac8de0a2947c1681d01a3b315725ce3f",
      "url": "https://github.com/BrianMF7/HackNight/blob/95e25cd4ac8de0a2947c1681d01a3b315725ce3f/.cursor/commands/test.md",
      "key": "BrianMF7/HackNight/.cursor/commands/test.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/brianmf7-hacknight-test-cursor-command/manifest?version=1.0.0

About

Use it

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