Answers from the documentation; checking which model is on duty
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.
Use when a user reports an active production incident with OpenSIPS (calls failing, registrations dropping, one-way audio, service crash, traffic spike).
Stabilisation action (what to run now to stop the bleed)
Root cause candidates (top 3, ranked by evidence)
Fix plan (ordered steps, including rollback)
Do not apply config changes in production without explicit user confirmation. Runtime MI commands (unblock, reload, resize) are okay after triage.
Use it
Installed into a catalogue, chosen by a router
Install opensips-incident-responder 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.
When a provider is down or over quota the request moves on; the trace says it did.
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 - nothing else to configurecurl-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}'# or pin it on the OpenAI-compatible endpoint: {"model": "opensips-opensips-mcp-server-opensips-incident-responder-3dec52", ...}
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
