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 YusukeShimizu/lightning-compute-protocol (AGENTS.md). Install upstream with npx skills add YusukeShimizu/lightning-compute-protocol. Copyright stays with the author.
AGENTS
Repository-wide agent guidance is centralized as repo-local Codex skills under .codex/skills/.
Use /skills to browse, or invoke explicitly by name (example: $lcp-repo).
If you are editing files under a subdirectory that contains its own AGENTS.md, treat the deepest AGENTS.md as a pointer to the relevant skill(s) for that scope.
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 lightning-compute-protocol 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.
