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 brndnmtthws/thetagang (.github/instructions/review-config.instructions.md). Copyright stays with the author.
Config and Migration Review Focus
When reviewing these files:
Preserve schema invariants: valid stage IDs, dependency ordering, no dependency cycles, and collect_state first/enabled.
Flag any change that weakens validation bounds/defaults for risk-sensitive settings (thresholds, margin usage, DTE/sigma limits).
Ensure migration remains deterministic and safe: backup handling, atomic writes, and no silent destructive overwrite.
Verify v2 config compatibility with legacy runtime conversion remains intact.
Require tests whenever new config keys are added, moved, renamed, or defaulted.
If CLI behavior changes around migration prompts/flags, require tests for non-interactive and error-reporting paths.
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.
