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.
federation-status - Skill - OpenSmartRoute
Skillv1.0.0
federation-status
Show federation health — peers, sessions, trust levels, and message metrics. Use when the user asks "is federation healthy?", "show peers", "federation status", or wants to inspect cross-installation…
Imported from ruvnet/ruflo (plugins/ruflo-federation/skills/federation-status/SKILL.md) via skills.sh. Install upstream with npx skills add ruvnet/ruflo --skill federation-status. Copyright stays with the author.
Show the current state of the federation.
Steps:
npx -y -p @claude-flow/plugin-agent-federation@latest ruflo-federation status -- overall health
npx -y -p @claude-flow/plugin-agent-federation@latest ruflo-federation peers -- list peers with trust levels and scores
Summarize: active sessions, messages exchanged, PII redactions, threat detections
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://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}'
Installed into a catalogue, chosen by a router
Install federation-status 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.
