Set Up Model Router
Model Router runs on the host and selects a model from a configured pool for each request.
OpenShell registers it as an OpenAI-compatible provider while the sandbox remains on inference.local.
How the Router Fits
The Model Router option uses the routed inference profile in nemoclaw-blueprint/blueprint.yaml.
During onboarding, NemoClaw starts the router proxy on host port 4000, waits for its health endpoint, and registers the nvidia-router provider with OpenShell.
The sandbox does not call port 4000 directly.
Credentials flow through the OpenShell provider system. The sandbox never sees raw API keys.
Configure the Model Pool
The router model pool lives in nemoclaw-blueprint/router/pool-config.yaml.
Edit that file to define the model names that the router can select.
The default pool routes between NVIDIA-hosted Nemotron models.
It uses tolerance to select the lowest-cost model whose predicted quality stays within the configured threshold.
Use these values to tune the accuracy and cost tradeoff.
Meet the Python Requirement
NemoClaw creates a host-side virtual environment for Model Router during onboarding.
It probes python3.13, python3.12, python3.11, python3.10, and python3 in that order.
The selected interpreter must have a version in the range [3.10, 3.14) and must import ensurepip, pyexpat, ssl, and venv without error.
If no candidate qualifies, onboarding stops and prints the failure for each candidate.
Set NEMOCLAW_MODEL_ROUTER_PYTHON to an absolute path to probe only one interpreter.
The pin is strict. NemoClaw rejects relative command names and stops with the failure reason if the selected interpreter does not qualify.
Onboard Non-Interactively
Set the routed provider and NVIDIA credential before running onboarding.
Related Topics
- About Inference Routing explains the host and sandbox boundary.
- View the Active Inference Route shows the active provider and model.