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.
manifest - Skill - OpenSmartRoute
Skillv1.0.0
manifest
This directory contains manifest-defined execution, validation, persistence, and step handling for agent-authored modules.
Imported from xmanatee/kota (src/core/manifest/AGENTS.md). Install upstream with npx skills add xmanatee/kota --skill manifest. Copyright stays with the author.
Manifest
This directory contains manifest-defined execution, validation, persistence, and step handling for agent-authored modules.
Manifest modules provide a declarative way for agents to create persistent custom tools via JSON (module_factory).
The manifest format supports tools, name, version, description, and dependencies.
Automation belongs in contributed workflows and tools, not in the manifest format.
If a capability belongs to the shared step language or workflow runtime instead, move it there instead of duplicating semantics.
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 manifest 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.
