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 yuankuns/amaebi (AGENTS.md). Install upstream with npx skills add yuankuns/amaebi. Copyright stays with the author.
AGENTS.md
Startup behavior
Read this file first.
For coding workflow rules, read DEV_WORKFLOW.md.
On-demand operations docs (do not preload all)
When task is about deployment/config/troubleshooting, read OPERATIONS_INDEX.md first, then only the referenced file(s):
DEPLOYMENT.md
CONFIG_REFERENCE.md
RUNBOOK.md
Execution policy
Use scripts/test.sh for standard verification.
Use scripts/test.sh --docker for ignored/docker integration tests.
Keep work on task-specific worktrees; do not modify master directly.
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 amaebi 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.
