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.
pua-off - Skill - OpenSmartRoute
Skillv1.0.0
pua-off
PUA off alias for Codex. Codex subcommand mapping for Claude Code /pua:off style usage; invoke with $pua-off.
Imported from tanweai/pua (codex/pua-off/SKILL.md). Install upstream with npx skills add tanweai/pua --skill pua-off. Copyright stays with the author (MIT).
pua-off
This is a Codex CLI alias for the Claude Code /pua:off command.
Disable PUA always-on mode by setting ~/.pua/config.json always_on=false and feedback_frequency=0. Then report [PUA OFF].
When this alias changes ~/.pua/config.json, preserve unknown fields and create ~/.pua/ if missing. Do not claim completion without command/output evidence.
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://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 pua-off 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.
