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

cleanup-file-integrated - Prompt - OpenSmartRoute

Promptv1.0.0

cleanup-file-integrated

Name: cleanup-file-integrated
Author: betsyherbert

Clean up the currently open Python file in an integration-safe way.

by betsyherbert(0) 0 installs

Free

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

See reviews

About

Prompt file imported from betsyherbert/cortical_development (.cursor/commands/cleanup-file-integrated.md). Copyright stays with the author.

Clean up the currently open Python file in an integration-safe way.

Scope:

primary focus on this file
you may read and modify other files if needed to preserve compatibility

Allowed changes:

simplify logic
improve naming
refactor internal structure
change function or class interfaces IF:
- all call sites are updated
- behavior is preserved

Constraints:

scientific behavior must not change
diffs must remain readable
no architectural redesigns

Process:

Identify any interface changes required.
Update all dependent code.
Run relevant tests if available.

Output:

Summary of changes
List of files modified
Confirmation that compatibility was preserved

Use it

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

Clean up the currently open Python file in an integration-safe way.

Scope:
- primary focus on this file
- you may read and modify other files if needed to preserve compatibility

Allowed changes:
- simplify logic
- improve naming
- refactor internal structure
- change function or class interfaces IF:
  - all call sites are updated
  - behavior is preserved

Constraints:
- scientific behavior must not change
- diffs must remain readable
- no architectural redesigns

Process:
1. Identify any interface changes required.
2. Update all dependent code.
3. Run relevant tests if available.

Output:
1. Summary of changes
2. List of files modified
3. Confirmation that compatibility was preserved

Installed into a catalogue, chosen by a router

Install cleanup-file-integrated 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.

betsyherbert-cortical-development-cleanup-file-integrate-7bab53.prompt.jsonjson

{
  "prompt": "Clean up the currently open Python file in an integration-safe way.\n\nScope:\n- primary focus on this file\n- you may read and modify other files if needed to preserve compatibility\n\nAllowed changes:\n- simplify logic\n- improve naming\n- refactor internal structure\n- change function or class interfaces IF:\n  - all call sites are updated\n  - behavior is preserved\n\nConstraints:\n- scientific behavior must not change\n- diffs must remain readable\n- no architectural redesigns\n\nProcess:\n1. Identify any interface changes required.\n2. Update all dependent code.\n3. Run relevant tests if available.\n\nOutput:\n1. Summary of changes\n2. List of files modified\n3. Confirmation that compatibility was preserved",
  "variables": [],
  "notes": "Clean up the currently open Python file in an integration-safe way.",
  "metadata": {
    "source": {
      "provider": "github-cursor-commands",
      "repository": "https://github.com/betsyherbert/cortical_development",
      "path": ".cursor/commands/cleanup-file-integrated.md",
      "ref": "c69351d43a13a8393593261a782bc7e89c802937",
      "url": "https://github.com/betsyherbert/cortical_development/blob/c69351d43a13a8393593261a782bc7e89c802937/.cursor/commands/cleanup-file-integrated.md",
      "key": "betsyherbert/cortical_development/.cursor/commands/cleanup-file-integrated.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/betsyherbert-cortical-development-cleanup-file-integrate-7bab53/manifest?version=1.0.0

About

Use it

Install cleanup-file-integrated 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