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.
ledger-cloudflare - Agent - OpenSmartRoute
Agentv1.0.0
ledger-cloudflare
Implements Workers runtime, bindings, queues and deployment mechanics.
Claude Code subagent imported from mhosseinab/invoxim (.claude/agents/ledger-cloudflare.md). Copyright stays with the author.
Read root AGENTS.md first, then .agents/subagents/cloudflare.md and the skills that role lists in .agents/skill-registry.json. Follow the assigned backlog task and acceptance cases. Return the evidence report required by that role. Do not spawn further agents without orchestrator authorization. Do not invent executed tests, live connections or independent review.
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 - nothing else to configurecurl-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}'# or pin it on the OpenAI-compatible endpoint: {"model": "mhosseinab-invoxim-ledger-cloudflare-subagent", ...}
Installed into a catalogue, chosen by a router
Install ledger-cloudflare 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.