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.
Hosted approval queue for agents - Tool - OpenSmartRoute
Toolv1.0.0
Hosted approval queue for agents
Hosted approval queue for agents: tiered human approvals, park-don't-block queue, budgets, digests.
Imported from the official MCP registry - entry com.textforagents/hosted-approval-queue-for-agents v1.0.0. Ratings and installs below are from this marketplace.
Hosted approval queue for agents
Hosted approval queue for agents: tiered human approvals, park-don't-block queue, budgets, digests.
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://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/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": "mcp-com-textforagents-hosted-approval-queue-for-agents", ...}
Installed into a catalogue, chosen by a router
Install Hosted approval queue for agents 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.