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

respond-to-local-review - Prompt - OpenSmartRoute

Promptv1.0.0

respond-to-local-review

Name: respond-to-local-review
Author: JongEunLee310

Read docs/reviews/pr-<PR_NUMBER>.md, the PR diff, and the original Codex handoff task.

by JongEunLee310(0) 0 installs

Free

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

See reviews

About

Prompt file imported from JongEunLee310/ai-assisted-dev-template (.codex/prompts/respond-to-local-review.md). Copyright stays with the author.

Respond To Local Review

Read docs/reviews/pr-<PR_NUMBER>.md, the PR diff, and the original Codex handoff task.

Address blocking issues first. Keep suggestions separate from required changes. Do not broaden scope unless Claude Code or the human explicitly requests it.

Do not open a new PR for review fixes. Push the fix to the same feature branch (updating the existing PR) and record the follow-up as a comment on that PR.

Use it

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

# Respond To Local Review

Read `docs/reviews/pr-<PR_NUMBER>.md`, the PR diff, and the original Codex handoff task.

Address blocking issues first. Keep suggestions separate from required changes. Do not broaden scope unless Claude Code or the human explicitly requests it.

Do not open a new PR for review fixes. Push the fix to the same feature branch (updating the existing PR) and record the follow-up as a comment on that PR.

Manifest

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

Installed into a catalogue, chosen by a router

Install respond-to-local-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.

jongeunlee310-ai-assisted-dev-template-respond-to-local-476beb.prompt.jsonjson

{
  "prompt": "# Respond To Local Review\n\nRead `docs/reviews/pr-<PR_NUMBER>.md`, the PR diff, and the original Codex handoff task.\n\nAddress blocking issues first. Keep suggestions separate from required changes. Do not broaden scope unless Claude Code or the human explicitly requests it.\n\nDo not open a new PR for review fixes. Push the fix to the same feature branch (updating the existing PR) and record the follow-up as a comment on that PR.",
  "variables": [],
  "notes": "Read `docs/reviews/pr-<PR_NUMBER>.md`, the PR diff, and the original Codex handoff task.",
  "metadata": {
    "source": {
      "provider": "github-codex-prompts",
      "repository": "https://github.com/JongEunLee310/ai-assisted-dev-template",
      "path": ".codex/prompts/respond-to-local-review.md",
      "ref": "ed486d4c0db1fd97c3e4bcc7b8be3094c1732853",
      "url": "https://github.com/JongEunLee310/ai-assisted-dev-template/blob/ed486d4c0db1fd97c3e4bcc7b8be3094c1732853/.codex/prompts/respond-to-local-review.md",
      "key": "JongEunLee310/ai-assisted-dev-template/.codex/prompts/respond-to-local-review.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/jongeunlee310-ai-assisted-dev-template-respond-to-local-476beb/manifest?version=1.0.0

About

Respond To Local Review

Use it

Manifest

Install respond-to-local-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

Reviews