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 ziliangpeng/cyborg (AGENTS.md). Install upstream with npx skills add ziliangpeng/cyborg. Copyright stays with the author.
Cyborg Project Memory
Git Workflow
Always create a new branch from latest main for any changes to this repo (fetch first to ensure latest: git fetch origin main && git branch <new-branch> origin/main)
Never commit directly to main
Use feature branches with descriptive names (e.g., feat/halftone-image-processing)
Build System
This monorepo uses Bazel for building and managing dependencies.
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 cyborg 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.
