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.
Imported from diegosouzapw/awesome-omni-skill (skills/cli-automation/agentuity-cli-auth-org-current/SKILL.md). Install upstream with npx skills add diegosouzapw/awesome-omni-skill --skill agentuity-cli-auth-org-current. Copyright stays with the author (Apache-2.0).
Auth Org Current
Show the current default organization
Usage
agentuity auth org current
Examples
Show default organization:
bunx @agentuity/cli auth org current
Show output in JSON format:
bunx @agentuity/cli auth org current --json
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
Installed into a catalogue, chosen by a router
Install agentuity-cli-auth-org-current 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.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-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}'
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
