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.
llm - Skill - OpenSmartRoute
Skillv1.0.0
llm
Multi-provider LLM integration. Unified interface for OpenAI, Anthropic, Google, and local models.
Imported from sundial-org/awesome-openclaw-skills (skills/llm/SKILL.md). Install upstream with npx skills add sundial-org/awesome-openclaw-skills --skill llm. Copyright stays with the author.
LLM 🔮
Multi-provider Large Language Model integration.
Supported Providers
OpenAI (GPT-4, GPT-4o)
Anthropic (Claude)
Google (Gemini)
Local models (Ollama, LM Studio)
Features
Unified chat interface
Model comparison
Token counting
Cost estimation
Streaming responses
Usage Examples
"Compare GPT-4 vs Claude on this task"
"Use local Llama model"
"Estimate tokens for this prompt"
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 - 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 llm 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.