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 Zuixi/oh-my-md (.cursor/rules/rust.mdc). Copyright stays with the author.
Rust
cargo fmt. snake_case modules/fns; PascalCase types; SCREAMING_SNAKE_CASE consts. lib.rs is a facade. /// on all pub items.
Libraries: thiserror + Result. Bins may use anyhow. Minimize unsafe; wrap with // SAFETY:.
Secrets via std::env::var. cargo audit on dep changes. Bound untrusted JSON. Canonicalize paths inside an allow-list dir.
Unit tests in-file; integration in tests/; doctests on public API. No shared mutable globals.
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 rust 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.
