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.
oc-api-gateway - Skill - OpenSmartRoute
Skillv1.0.0
oc-api-gateway
API gateway for calling third-party APIs with managed auth.
Imported from luokai0/ai-agent-skills-by-luo-kai (ai-agent-skills/05-devops-and-cloud (by Luo Kai)/14-other-devops/oc-api-gateway/SKILL.md). Install upstream with npx skills add luokai0/ai-agent-skills-by-luo-kai --skill oc-api-gateway. Copyright stays with the author.
Api Gateway
Overview
API gateway for calling third-party APIs with managed auth.
API gateway for calling third-party APIs with managed auth.
Best Practices
Test in sandbox environment first
Check latest version before production use
Review source docs for advanced configuration
Related Skills
agent-installer
clawhub-publisher
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://api.opensmartroute.ai/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 oc-api-gateway 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.