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.
blucli - Skill - OpenSmartRoute
Skillv1.0.0
blucli
BluOS CLI (blu) for discovery, playback, grouping, and volume.
Imported from openclaw/openclaw (skills/blucli/SKILL.md) via skills.sh. Install upstream with npx skills add openclaw/openclaw --skill blucli. Copyright stays with the author.
blucli (blu)
Use blu to control Bluesound/NAD players.
Quick start
blu devices (pick target)
blu --device <id> status
blu play|pause|stop
blu volume set 15
Target selection (in priority order)
--device <id|name|alias>
BLU_DEVICE
config default (if set)
Common tasks
Grouping: blu group status|add|remove
TuneIn search/play: blu tunein search "query", blu tunein play "query"
Prefer --json for scripts. Confirm the target device before changing playback.
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 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 blucli 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.
