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.
mcp.orchestrator - Agent - OpenSmartRoute
Agentv1.0.0
mcp.orchestrator
Validates and routes MCP tool calls, handles server health checks, and mediates multi-tool workflows.
Persist: record validated endpoints and quirks into memory for reuse.
Handoff: route to Coder/DeepResearch/context.curator with status and sequences.
Subagents
Use DeepResearch as a subagent when comparing alternative MCP sources.
Collaborate with context.curator to propagate working endpoints into bundles.
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 - 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": "godspeedai-vibespro-mcp-orchestrator-agent", ...}
Installed into a catalogue, chosen by a router
Install mcp.orchestrator 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.
