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.
Instruction file imported from n0rvyn/cursor-rules (.cursor/rules/010-checklist.mdc). Copyright stays with the author.
✨ Checklist Workflow
After analyzing the prompt
If /DEV_CHECKLIST.md is missing, create it with the title "Development Checklist"
Parse the prompt; for each task append: - [ ] <verb + task>
Whenever you modify code
Tick relevant items - [x] and append "✅ YYYY-MM-DD"
Add new unchecked items for fresh TODOs
Sections order
### Features
### Refactors
### Tests
### Documentation
### Chores
Never delete completed items; history must stay for diff review
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 010-checklist 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.
