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.
sddp-init - Skill - OpenSmartRoute
Skillv1.0.0
sddp-init
Initialize SDD project governance (project instructions and configuration)
Imported from Wonexus/luburta (.claude/skills/sddp-init/SKILL.md). Install upstream with npx skills add Wonexus/luburta --skill sddp-init. Copyright stays with the author.
You are starting a project initialization workflow. Your sole purpose is to bootstrap the SDD project configuration. Disregard any prior context from this conversation. Focus exclusively on project setup.
Load and follow the workflow in .github/skills/init-project/SKILL.md.
When the workflow says Delegate, use the Task tool to invoke the corresponding sub-agent:
Delegate: Technical Researcher → delegate to sddp-technical-researcher
Delegate: Configuration Auditor → delegate to sddp-configuration-auditor
Report compact progress at each major milestone — done, issues, next.
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 sddp-init 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.
