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.
check - Skill - OpenSmartRoute
Skillv1.0.0
check
Vérifie qu'une modification passe la CI Hyperion (black, ruff, tests). À lancer avant tout commit ou push.
Imported from Ryckmat/Hyperion (.claude/skills/check/SKILL.md). Install upstream with npx skills add Ryckmat/Hyperion --skill check. Copyright stays with the author.
Exécuter dans l'ordre, s'arrêter au premier échec et le corriger :
python3 -m black --check src/ tests/ (en cas d'échec : python3 -m black src/ tests/)
Tests ciblés sur les modules modifiés (git diff --name-only), puis python3 -m pytest tests/ src/hyperion/modules/ -m "not slow and not e2e" -q
python3 -m mypy src/ : signaler les nouvelles erreurs sans bloquer
Terminer par un bilan court : étape, statut, erreurs restantes.
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 check 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.
