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 horacehylee/shutd (AGENTS.md). Install upstream with npx skills add horacehylee/shutd. Copyright stays with the author.
AGENTS.md
Build & deploy
go build -ldflags "-H=windowsgui" -o shutd.exe ./cmd/shutd only compiles a
binary to the given output path. It does not update the deployed binary.
go install -ldflags "-H=windowsgui" ./cmd/shutd builds and installs to
%GOPATH%\bin\shutd.exe.
%GOPATH%\bin\shutd.exe is the deployment target: the startup shutd.vbs
(see README) launches the app from there.
When asked to "build it" (or equivalent), treat that as build and
install — a repo-root build alone leaves the startup binary stale.
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 slotcurl-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 shutd 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.
