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.
alpha - Skill - OpenSmartRoute
Skillv1.0.0
alpha
Fixture dispatcher with a mode table and forced-read references.
Imported from garrytan/gstack (test/fixtures/context-bill/tree-a/alpha/SKILL.md). Install upstream with npx skills add garrytan/gstack --skill alpha. Copyright stays with the author.
Alpha
Dispatch protocol
Infer the mode from the request.
Read references/CORE.md and references/POLICY.md for every invocation. Read references/OPTIONAL.md before public-web work.
When the target is a repository, read references/CORE.md once before specialist work; it is already billed eagerly.
Top-level modes
Mode
Infer when
Candidate internal specialists
Discovery
The idea is fluid.
references/legacy/office.md
Full chain
Everything at once.
references/legacy/auto.md
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 alpha 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.
