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.
structure-policy - Skill - OpenSmartRoute
Skillv1.0.0
structure-policy
Follow the repository structure policy before creating, moving, or deleting files.
Instruction file imported from A-Baji/ClipMorph (.github/instructions/structure-policy.instructions.md). Copyright stays with the author.
Read and follow the repository-local structure policy in docs/structure-policy.md before creating, moving, or deleting files.
Prefer the repository’s established boundaries (clipmorph/, tests/, docs/, frontend/) over new top-level directories, and keep generated runtime state such as build/, clipmorph.egg-info/, input/, output/, and uploads/ out of source changes. Update this policy when the project architecture intentionally changes.
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 structure-policy 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.
