Answers from the documentation; checking which model is on duty
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.
ruflo-doctor - Skill - OpenSmartRoute
Skillv1.0.0
ruflo-doctor
Run health checks on the Ruflo installation and fix common issues
Imported from ruvnet/ruflo (plugins/ruflo-core/skills/ruflo-doctor/SKILL.md) via skills.sh. Install upstream with npx skills add ruvnet/ruflo --skill ruflo-doctor. Copyright stays with the author.
Run npx @claude-flow/cli@latest doctor --fix to diagnose and auto-repair common issues.
Checks: Node.js 20+, npm 9+, git, config validity, daemon status, memory database, API keys, MCP servers, disk space, TypeScript.
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 slotcurl-s-X POST https://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/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 ruflo-doctor 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.
