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.
generated-docs - Skill - OpenSmartRoute
Skillv1.0.0
generated-docs
Prefer generated documentation when code, CLI metadata, schema, or protocol models are the source of truth.
Instruction file imported from tikoci/centrs (.github/instructions/generated-docs.instructions.md). Copyright stays with the author.
Generated docs
Prefer generated documentation when code, CLI metadata, schema, or protocol models are the source of truth.
Write typed exports, JSDoc, command metadata, and schemas so TypeDoc and the CLI-doc generator (scripts/gen-cli-docs.ts → docs/CLI.md) can reuse them.
Avoid copying option tables by hand across README, API docs, MCP docs, and help output.
Human-authored docs should explain concepts, workflow, and decisions that cannot be generated reliably.
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}'
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
