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.

setup - Skill - OpenSmartRoute

Name: setup
Author: ZoolCoder

Imported from ZoolCoder/zc-care (plugin/skills/setup/SKILL.md). Install upstream with npx skills add ZoolCoder/zc-care --skill setup. Copyright stays with the author (MIT).

Set up

Install: brew tap zoolcoder/zc-care https://github.com/zoolcoder/zc-care, then brew install --cask zc-care, or go install github.com/zoolcoder/zc-care/cmd/zc-care@latest.
Write ~/.config/zc-care/zc-care.yaml, or keep it in the user's dotfiles repository and pass -config. Start from zc-care.example.yaml. Each target needs a kebab-case name and a provider: packages and tools need a file, dotfiles needs a source.
Run zc-care validate, then zc-care doctor. Fix every fail line before planning. A program line that fails names a tool to install: Homebrew, chezmoi or mise. Ask before installing it.
Hand over to the plan-apply skill for the first plan.

Never point a dotfiles target at the user's real home directory while another tool (such as an older dotfiles script) still manages it: set destination to a scratch directory until the user switches over.

Never create a target with prune: true on a directory the user did not name: prune deletes every file the config does not declare.

# 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}'

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

{ "ocm": "1", "id": "zoolcoder-zc-care-setup", "kind": "skill", "name": "setup", "description": "Install zc-care, write a first config and check it with doctor. Use when the user asks to \"set up\", \"install\" or \"get started with\" zc-care, or when doctor fails.", "publisher": "ZoolCoder", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Install zc-care, write a first config and check it with doctor. Use when the user asks to \"set up\", \"install\" or \"get started with\" zc-care, or when doctor fails." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/ZoolCoder/zc-care", "path": "plugin/skills/setup/SKILL.md", "ref": "c9fa8bfdb808b7bae3670a20b6cd1f11cd280f22", "url": "https://github.com/ZoolCoder/zc-care/blob/c9fa8bfdb808b7bae3670a20b6cd1f11cd280f22/plugin/skills/setup/SKILL.md", "key": "ZoolCoder/zc-care/plugin/skills/setup/SKILL.md" }, "compatibility": "Needs macOS, with Homebrew or Go.", "license": "MIT" }, "instructions": "# Set up\n\n1. Install: `brew tap zoolcoder/zc-care https://github.com/zoolcoder/zc-care`, then `brew install --cask zc-care`, or `go install github.com/zoolcoder/zc-care/cmd/zc-care@latest`.\n2. Write `~/.config/zc-care/zc-care.yaml`, or keep it in the user's dotfiles repository and pass `-config`. Start from `zc-care.example.yaml`. Each target needs a kebab-case `name` and a `provider`: `packages` and `tools` need a `file`, `dotfiles` needs a `source`.\n3. Run `zc-care validate`, then `zc-care doctor`. Fix every `fail` line before planning. A `program` line that fails names a tool to install: Ho", "cost": { "context_tokens": 263 } }

setup

About

Set up

Use it

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