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

status-sync - Skill - OpenSmartRoute

Skillv1.0.0

status-sync

Name: status-sync
Author: httpsJMDV

Verify the Status section of CLAUDE.md against git and the real code, then report corrections. Use at the start of a session or after a PR merges.

by httpsJMDV(0) 0 installs

Free

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

See reviews

About

Imported from httpsJMDV/basta_velure (.claude/skills/status-sync/SKILL.md). Install upstream with npx skills add httpsJMDV/basta_velure --skill status-sync. Copyright stays with the author.

Read-only check, then correct only the Status section of CLAUDE.md if the user agrees or has said to just fix it.

git fetch origin, then compare main to origin/main (local main is often stale).
git log --oneline -40 origin/main and git branch -r --no-merged origin/main to list what is merged and what is not.
For each "Done" or "In progress" item, find evidence in code or docs/api/*.md (routes in backend/routes/api.php, pages in frontend/src/pages, tests in backend/tests/Feature). Say "unverified" when you cannot find it.
Check whether the next feature already has code, a branch, or a placeholder route.
Report: confirmed items, wrong items, stale branches, and the exact text you would change. Do not touch code.

Use it

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

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Installed into a catalogue, chosen by a router

Install status-sync 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

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

httpsjmdv-basta-velure-status-sync.ocm.jsonjson

{
  "ocm": "1",
  "id": "httpsjmdv-basta-velure-status-sync",
  "kind": "skill",
  "name": "status-sync",
  "description": "Verify the Status section of CLAUDE.md against git and the real code, then report corrections. Use at the start of a session or after a PR merges.",
  "publisher": "httpsJMDV",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "coding"
    ],
    "tags": [
      "skill-md",
      "github"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Verify the Status section of CLAUDE.md against git and the real code, then report corrections. Use at the start of a session or after a PR merges."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github",
      "repository": "https://github.com/httpsJMDV/basta_velure",
      "path": ".claude/skills/status-sync/SKILL.md",
      "ref": "dc23c139187947d6f975553ce81cb9a2351e635a",
      "url": "https://github.com/httpsJMDV/basta_velure/blob/dc23c139187947d6f975553ce81cb9a2351e635a/.claude/skills/status-sync/SKILL.md",
      "key": "httpsJMDV/basta_velure/.claude/skills/status-sync/SKILL.md"
    }
  },
  "instructions": "Read-only check, then correct only the Status section of CLAUDE.md if the user agrees or has said to just fix it.\n\n1. `git fetch origin`, then compare `main` to `origin/main` (local main is often stale).\n2. `git log --oneline -40 origin/main` and `git branch -r --no-merged origin/main` to list what is merged and what is not.\n3. For each \"Done\" or \"In progress\" item, find evidence in code or `docs/api/*.md` (routes in `backend/routes/api.php`, pages in `frontend/src/pages`, tests in `backend/tests/Feature`). Say \"unverified\" when you cannot find it.\n4. Check whether the next feature already has",
  "cost": {
    "context_tokens": 188
  }
}

Fetch it by URL: GET /api/v1/registry/httpsjmdv-basta-velure-status-sync/manifest?version=1.0.0

About

Use it

Install status-sync 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