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 ssrjkk/claude-skills (.claude/skills/networking/nat-automation/SKILL.md). Install upstream with npx skills add ssrjkk/claude-skills --skill nat-automation. Copyright stays with the author.
NAT Automation
Automation with NAT. network automation.
Quick Start
NAT Automation
See NAT docs
When to Use
network automation
scripting
IaC
Step-by-Step
Set up NAT
Configure Automation
Implement features
Test and verify
Deploy and monitor
Dependencies
No external dependencies required: No external dependencies
Examples
NAT Automation
See NAT documentation
Resources
Best practices and guidelines
Industry standards
Validation
nat --version
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 nat-automation 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.
