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

ship - Prompt - OpenSmartRoute

Promptv1.0.0

ship

Name: ship
Author: EnterpriseGlue

Push and merge an explicitly authorized code capability without publication

by EnterpriseGlue(0) 0 installs

Free

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

See reviews

About

Prompt file imported from EnterpriseGlue/enterpriseglue-the-bridge-oss (.windsurf/workflows/ship.md). Copyright stays with the author.

/ship

Use the maintained enterpriseglue-ship skill at plugins/enterpriseglue-dev-workflows/skills/enterpriseglue-ship/SKILL.md.

This command ships one coherent code capability through local gates and protected PR checks. Preserve per-change release fragments, package-version discipline and documentation-boundary validation.

Release Please PRs belong to /release. Do not merge them, enable their auto-merge, create tags or dispatch publication from /ship. Report the code merge and unreleased state; deployment remains separately authorized.

Use it

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

# /ship

Use the maintained `enterpriseglue-ship` skill at
`plugins/enterpriseglue-dev-workflows/skills/enterpriseglue-ship/SKILL.md`.

This command ships one coherent code capability through local gates and
protected PR checks. Preserve per-change release fragments, package-version
discipline and documentation-boundary validation.

Release Please PRs belong to `/release`. Do not merge them, enable their
auto-merge, create tags or dispatch publication from `/ship`. Report the code
merge and unreleased state; deployment remains separately authorized.

Installed into a catalogue, chosen by a router

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

enterpriseglue-enterpriseglue-the-bridge-oss-ship-workflow.prompt.jsonjson

{
  "prompt": "# /ship\n\nUse the maintained `enterpriseglue-ship` skill at\n`plugins/enterpriseglue-dev-workflows/skills/enterpriseglue-ship/SKILL.md`.\n\nThis command ships one coherent code capability through local gates and\nprotected PR checks. Preserve per-change release fragments, package-version\ndiscipline and documentation-boundary validation.\n\nRelease Please PRs belong to `/release`. Do not merge them, enable their\nauto-merge, create tags or dispatch publication from `/ship`. Report the code\nmerge and unreleased state; deployment remains separately authorized.",
  "variables": [],
  "notes": "Push and merge an explicitly authorized code capability without publication",
  "metadata": {
    "source": {
      "provider": "github-windsurf-workflows",
      "repository": "https://github.com/EnterpriseGlue/enterpriseglue-the-bridge-oss",
      "path": ".windsurf/workflows/ship.md",
      "ref": "2fe768c1c5b1c11e93bf6a783527f44faa8bdd68",
      "url": "https://github.com/EnterpriseGlue/enterpriseglue-the-bridge-oss/blob/2fe768c1c5b1c11e93bf6a783527f44faa8bdd68/.windsurf/workflows/ship.md",
      "key": "EnterpriseGlue/enterpriseglue-the-bridge-oss/.windsurf/workflows/ship.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/enterpriseglue-enterpriseglue-the-bridge-oss-ship-workflow/manifest?version=1.0.0

ship

About

/ship

Use it

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