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.
Instruction file imported from themotionvisual/ViewTubeBUILD (.cursor/rules/viewtube-youtube-editor-system.mdc). Copyright stays with the author.
For ViewTube editor work, read docs/editor/VIEWTUBE_YOUTUBE_EDITOR_SYSTEM_MASTER_RESOURCE.md and follow skills/viewtube-youtube-editor-system/SKILL.md.
Use one desktop/mobile project model. BrainRuntime owns creator AI reasoning/orchestration; Video Director owns async media generation; Asset Engine/Vault owns generated asset provenance; Remotion owns deterministic render/time.
Before handoff, update Current Work and append the living master resource Update Log with branch/PR/commit, paths, verification, references, status, and next action.
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 viewtube-youtube-editor-system 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.
