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.
Imported from xhyperium/infra.rs (crates/adapters/storage/clickhouse/AGENTS.md). Install upstream with npx skills add xhyperium/infra.rs --skill clickhouse. Copyright stays with the author.
远程 HTTP 必须 fail-closed;HTTPS 使用 rustls roots 与可选 PEM CA
本地 TLS 协议实验不等于真实 ClickHouse 集群 TLS 证据
未验证集群 / 原生协议前禁止宣称 package stable
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 clickhouse 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.