Switch Inference Providers

Move a sandbox to another provider family while keeping the OpenShell route, agent configuration, and host registry aligned. Use onboarding first when the target is neither compatible-endpoint nor compatible-anthropic-endpoint and is not registered. The compatible endpoint workflow below can register an absent custom provider from complete route metadata.

Find a Registered Provider

List the configured provider credentials when you need the provider ID.

nemoclaw credentials list

inference set also accepts installer-facing provider names such as anthropicCompatible, build, custom, and llama-cpp. NemoClaw normalizes an accepted alias to its canonical OpenShell provider ID and records the canonical name in the sandbox registry.

If the requested provider is unsupported, NemoClaw lists selectable supported provider IDs registered on the selected gateway. If it cannot read the gateway list, it lists every supported provider ID instead.

If OpenShell cannot find a requested provider other than compatible-endpoint or compatible-anthropic-endpoint, NemoClaw leaves the route and sandbox state unchanged. Run nemoclaw onboard to register the provider, then retry the switch. For a compatible custom endpoint, pass the complete route metadata described below so NemoClaw can register the provider.

Switch the Provider at Runtime

Pass the target provider and model together. Target a non-default sandbox by name. inference set takes --sandbox <name>.

nemoclaw inference set --provider <provider> --model <model> --sandbox <name>

For OpenClaw, NemoClaw updates the provider namespace and selected model in the running configuration. Changes within the current API family hot-reload without replacing the gateway process. When the API family changes, NemoClaw commits the route and configuration, then restarts only the OpenClaw gateway and verifies its health. After every changed synchronized route, NemoClaw verifies that the local CLI device has the managed gateway’s required pairing scopes before it reports success. If pairing does not converge, the route and configuration remain committed. Run nemoclaw <name> doctor --fix, then retry the agent turn.

If the in-sandbox configuration sync fails after the gateway route changes, NemoClaw keeps the gateway and host registry aligned and prints a rebuild hint. Run the rebuild before relying on the running agent.

Use --no-verify only when OpenShell cannot verify the target provider at switch time and you have already confirmed its provider and credential. This flag does not bypass shared-gateway compatibility checks. When you explicitly supply a direct compatible endpoint at http://host.openshell.internal:<port>, NemoClaw skips OpenShell’s host-side provider probe because that hostname resolves only inside the sandbox network. It then sends a validation request from the target sandbox before persisting the route in NemoClaw state. The output limit is 16 tokens for ordinary providers and 256 tokens for Google Gemini. For sandbox-only custom endpoints, NemoClaw waits 6 seconds for OpenShell’s route cache after changing the provider or model, then verifies the new route from inside the sandbox. When the switch also changes the API family and that request returns HTTP 400 or 404, NemoClaw retries up to two times after delays of 2 and 4 seconds. NemoClaw uses the same retry schedule when validation fails before it receives an HTTP status, such as while the gateway route is reloading. Each retry uses the same output limit for the selected provider. Other HTTP failures are not retried. If that request fails, NemoClaw attempts to restore the previous OpenShell selection and remove a provider that this switch created. If the error reports that rollback could not complete, rerun onboarding before using the route or retrying the switch. Endpoint-shape and shared-gateway compatibility checks still apply.

Handle Compatible Endpoints

When moving from another provider family to compatible-endpoint or compatible-anthropic-endpoint, provide the trusted endpoint URL and enough API metadata to record the complete route identity. Export the canonical credential environment variable for the target provider. Run this command from the host that owns the sandbox.

export COMPATIBLE_API_KEY="<api-key>"
nemoclaw inference set \
  --provider compatible-endpoint \
  --model <model-name> \
  --endpoint-url <trusted-url> \
  --credential-env COMPATIBLE_API_KEY \
  --inference-api openai-completions \
  --sandbox <name>

NemoClaw validates the endpoint before it changes the route. For an HTTPS IP-literal or DNS-pinned HTTP endpoint, NemoClaw registers and verifies an absent provider before selecting the route. If OpenShell still reports the provider as absent, NemoClaw retries the switch once. If provider verification or route selection fails, NemoClaw leaves the inference selection unchanged and removes the provider only when it can verify the revision created by this switch. If removal was not attempted or could not be confirmed, rerun onboarding before using that provider route or retrying the switch. For a DNS-backed HTTPS endpoint, NemoClaw registers the HTTPS Pin Runtime provider before the first route attempt.

Supported API-family values are openai-completions, anthropic-messages, and openai-responses. For a Hermes compatible-anthropic-endpoint target, omit --inference-api because NemoClaw selects openai-completions. An explicit different API family is rejected for that route.

To switch only the model for an existing compatible provider, omit the endpoint options. NemoClaw reuses the endpoint in the sandbox registry and verifies the selected route. To change a direct compatible provider’s custom endpoint or credential binding, re-run onboarding with the requested binding. inference set refuses to replace an existing direct binding because OpenShell does not expose the previous provider configuration required for rollback. A rebuild reuses the recorded endpoint and cannot change it.

DNS-backed HTTPS routes use an HTTPS Pin Runtime binding. Provider updates occur after OpenShell selects the new route. If sandbox verification fails after an existing provider update succeeds, NemoClaw restores the previous inference selection but leaves the updated provider binding in place. Rerun onboarding before using that provider route or retrying the switch. If an update fails, NemoClaw attempts to restore the previously recorded provider and model. If NemoClaw rejects the update before the provider command runs, the provider binding stays unchanged. After a provider command fails without confirming that no change occurred, provider state may be partial. If the error says that provider state may be partial, rerun onboarding to reconcile the provider before using the route or rerunning inference set. If NemoClaw cannot restore the previous selection, resolve the reported restore failure. Then rerun onboarding before you use the route.

Account for Shared Gateways

One gateway has one live route even when NemoClaw records different intended routes for its sandboxes. Review Use Shared Gateway Routes before changing a provider that another registered sandbox shares. Runtime inference set also refuses a change that would leave another registered sandbox with a different recorded route.

Related Topics

• View the Active Inference Route to inspect the route before and after a switch.
• Use Shared Gateway Routes when multiple sandboxes use one gateway.
• Switch Models when the provider does not change.
• Set Up an OpenAI-Compatible Endpoint to register a custom route through onboarding.