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.
core - Skill - OpenSmartRoute
Skillv1.0.0
core
Core project context for Smart City Booking Backend
Business logic in src/commons/, HTTP in src/platform/
English for code, comments, commits, PRs, and changelog entries
DRY: reuse existing code; extract shared logic only on real duplication
Run npm test and npm run lint:check before finishing
Minimal diffs, no drive-by refactors, no commits unless asked
Never commit secrets (.env)
Detailed guides: docs/agents/
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 core 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.
