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 numbata/grape-oas (.cursor/rules/core.mdc). Copyright stays with the author.
This repository uses AGENTS.md as its source of truth
for contributor rules. Follow it strictly. This rule file only adds
Cursor-specific reminders; everything else lives in AGENTS.md and the
agents/ docs.
Run bundle exec rake (test + rubocop) before opening a PR.
This project uses Minitest, not RSpec.
Use bundle exec rubocop -a for safe autocorrections; -A only after
reviewing unsafe ones.
Never modify CHANGELOG.md's released sections — only add to
## [Unreleased].
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 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.
