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.
transcriber - Skill - OpenSmartRoute
Skillv1.0.0
transcriber
Single-file push-to-talk daemon (`transcriber.c`): hold Right Ctrl, speak → transcript at the cursor.
Imported from yookibooki/transcriber (AGENTS.md). Install upstream with npx skills add yookibooki/transcriber. Copyright stays with the author.
Single-file push-to-talk daemon (transcriber.c): hold Right Ctrl, speak → transcript at the cursor.
Goal: simplest solution that just works.
Philosophy: extreme efficiency, idiomatic C — minimal RAM / binary / LOC / syscalls.
Hard Requirements
Metric
Requirement
Idle CPU
0 wakeups
Idle Memory
<200KB
Binary Size
<200KB
LOC
<1500
Compatibility
all distros, any arch
Build: ./build.sh
Tests
Agents run no tests. Build and ask user to test.
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 transcriber 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.
