> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/nemoclaw/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/nemoclaw/_mcp/server.

# Switch Inference Providers

> Move a NemoClaw-managed sandbox to another registered inference provider.

Move a sandbox to another provider family while keeping the OpenShell route, agent configuration, and host registry aligned.
Use onboarding first when the target provider is not registered.

## Find a Registered Provider

## Switch the Provider at Runtime

## Recreate a Deep Agents Sandbox

Deep Agents uses fresh sandbox recreation for provider changes.
The recreation validates the provider and rewrites `/sandbox/.deepagents/config.toml` with the OpenShell route.

```bash
nemo-deepagents onboard --fresh --name <sandbox-name> --recreate-sandbox
```

## Handle Compatible Endpoints

## Account for Shared Gateways

Every sandbox registered on one OpenShell gateway must use the same provider and model.
Custom routes must also use the same normalized endpoint and API family.
NemoClaw includes stopped sandboxes because they depend on that route when restarted.

When a route conflicts, NemoClaw exits before changing the gateway, agent configuration, or host registry and names the affected sandboxes.
Align the routes, remove a conflicting sandbox, or onboard it with another `NEMOCLAW_GATEWAY_PORT`.

Do not run `openshell inference set` directly on a shared NemoClaw gateway because that bypasses registry compatibility checks.

## Related Topics

* [View the Active Inference Route](view-active-inference-route) to inspect the route before and after a switch.
* [Switch Models](switch-models) when the provider does not change.
* [Set Up an OpenAI-Compatible Endpoint](../custom-endpoints/set-up-openai-compatible-endpoint) to register a custom route through onboarding.