← ScioNos

Claude Code with RouterLab

A ScioNos path from installation to your first call. Available models depend on your access and wrapper version.

1. Check prerequisites

Node.js ^22.13.0 or ≥23.5.0, installed Claude Code (≥2.1.220) and an active RouterLab key. On Linux, persistent secure storage requires secret-tool and an available Secret Service. Check your ScioNos version’s README for its requirements.

Terminal shell

node --version
claude --version

2. Install ScioNos and connect your key

Use the routerlab service. Login requests your key through a masked prompt. Keep it out of published commands. Diagnostics should confirm connectivity and a non-empty authorized catalog.

Terminal shell

npm install -g wrapper-scionos
wrapper-scionos --version
wrapper-scionos auth login --service routerlab
wrapper-scionos doctor --service routerlab

3. Choose your model and launch

For a trial account, choose the Trial strategy. Both the main model and subagent model must be authorized by your key and end in -trial. For a subscription, choose an available strategy. If no compatible model is offered, stop the launch and run diagnostics.

Terminal shell

wrapper-scionos claude-code --service routerlab --strategy trial

4. Complete your first launch

Open a test folder. Ask for a short answer without tools, then an authorized file read. You should receive a response and see usage in RouterLab. Exact output depends on the model.

Test prompt text

Reply “connection successful”. Then delegate reading this folder’s README to a subagent and summarize it in one sentence. Do not modify any files.

For your own HTTP or Python Messages integration, read the examples, SDK versions and route limitations. Claude Messages API guide

Limitations and troubleshooting

401: log in with your key again. 403 or empty catalog: check the plan, expiry and authorized models. 429: all keys and models share the quota; check your budget and reset. Fix a rejected subagent with an authorized model. Do not replace a Trial variant with a production route to bypass a rejection.

Tools, vision, streaming and reasoning depend on the model and protocol. Validate a small representative case before your project. Service destinations are fixed; custom base URL variables do not replace them.

Diagnostics shell

wrapper-scionos doctor --service routerlab
wrapper-scionos auth status --service routerlab

Logout and restore

Exit Claude Code, then log out to remove the key stored by ScioNos. The local proxy is tied to the launch session.

Terminal shell

wrapper-scionos auth logout --service routerlab

Audience measurement

Allow Google Analytics and RouterLab to measure public visits and link campaign sources to your signup? This is optional and can be changed at any time. If you decline, only anonymous visit totals are kept.