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.
frontend-feature - Skill - OpenSmartRoute
Skillv1.0.0
frontend-feature
Implement a bounded Turaco React/TypeScript UI feature after API/domain behavior is known.
Imported from MagicalWig34653/turaco (.claude/skills/frontend-feature/SKILL.md). Install upstream with npx skills add MagicalWig34653/turaco --skill frontend-feature. Copyright stays with the author.
Frontend Feature
Implement $ARGUMENTS using existing frontend/platform patterns.
Use localization keys for all user-facing text.
Reuse shared API/auth/permission/components.
Do not invent backend authorization semantics in UI state.
Preserve Turaco's low-friction employee UX and information-dense IT workspace principles.
Use brand accents for orientation, not as semantic state colors.
Add tests and run typecheck/lint/tests for touched 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 frontend-feature 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.
