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.
mux-video - Skill - OpenSmartRoute
Skillv1.0.0
mux-video
RETIRED 2026-07-15 — the Mux pipeline was replaced by wzrrd-video (fully Cloudflare-native). Use skills/wzrrd-video instead. Kept for historical Mux asset management only.
Imported from joelhooks/joelclaw (skills/mux-video/SKILL.md). Install upstream with npx skills add joelhooks/joelclaw --skill mux-video. Copyright stays with the author.
mux-video (RETIRED)
This pipeline was retired 2026-07-15. Video publishing is now fully Cloudflare-native
through wzrrd — see skills/wzrrd-video/SKILL.md. Existing Mux assets keep playing; use the
Mux API directly (credentials in agent-secrets: mux_token_id/mux_token_secret) only for
managing those historical assets. The Mux webhook registration at hooks.joelclaw.com is
vestigial (events verify and are dropped).
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 mux-video 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.
