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.
langgraph-docs - Skill - OpenSmartRoute
Skillv1.0.0
langgraph-docs
Fetches and references LangGraph Python documentation to build stateful agents, create multi-agent workflows, and implement human-in-the-loop patterns.
Imported from langchain-ai/deepagents (libs/code/examples/skills/langgraph-docs/SKILL.md) via skills.sh. Install upstream with npx skills add langchain-ai/deepagents --skill langgraph-docs. Copyright stays with the author.
This returns a structured list of all available documentation with descriptions.
2. Select Relevant Documentation
Identify 2-4 most relevant URLs from the index. Prioritize:
Implementation questions — specific how-to guides
Conceptual questions — core concept pages
End-to-end examples — tutorials
API details — reference docs
3. Fetch and Apply
Use fetch_url on the selected URLs, then complete the user's request using the documentation content.
If fetch_url fails or returns empty content, retry once. If it fails again, inform the user and suggest checking https://langchain-ai.github.io/langgraph/ directly.
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 langgraph-docs 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.
