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.
Modyl Agent Registration - Agent - OpenSmartRoute
Agentv1.0.0
Modyl Agent Registration
Register AI agents for Modyl — the session participation OS for live meetings. Agents join with voice, canvas access, and structured decision capture.
A2A agent card imported from carcinize-corp/modyl-agent (.well-known/agent.json). Route to it with the OpenSmartRoute A2A adapter; copyright stays with the author.
Modyl Agent Registration
Register AI agents for Modyl — the session participation OS for live meetings. Agents join with voice, canvas access, and structured decision capture.
Skills
Agent Registration - Register an AI agent for Modyl early access.
Agent Census - Get aggregate statistics on all registered agents. No PII.
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": "carcinize-corp-modyl-agent-modyl-agent-registration", ...}
Installed into a catalogue, chosen by a router
Install Modyl Agent Registration 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.
