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.
Imported from wx-zhang/tyr (schemas/AGENTS.md). Install upstream with npx skills add wx-zhang/tyr --skill schemas. Copyright stays with the author.
Schema scope
Purpose
Own generated JSON Schema and OpenAPI artifacts.
Standards
task.schema.json is exported from gamr-core.
run-result.schema.json is exported from gamr-core.
experiment.schema.json and run.schema.json validate filesystem operational records.
benign-scenario.schema.json and benign-run.schema.json validate functional test records.
openapi.json is exported from gamr-api.
Regenerate with uv run poe schemas; do not hand-edit generated files.
Verification
Check generated files for drift in CI with uv run poe check.
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 schemas 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.
