Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
desktop - Skill - OpenSmartRoute
Skillv1.0.0
desktop
Use [CLAUDE.md](CLAUDE.md) for desktop architecture, build commands, and testing conventions.
Imported from autonomous-ai/openharness (desktop/AGENTS.md). Install upstream with npx skills add autonomous-ai/openharness --skill desktop. Copyright stays with the author.
Desktop development
Use CLAUDE.md for desktop architecture, build commands, and testing
conventions.
Before adding or changing a terminal-workspace dialog, picker, form, or preview,
read and follow the terminal dialog design system.
Its core rule is fixed cells, plain text, one-line selection. It supersedes
older visual handoff notes for these surfaces.
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 desktop 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.
