Documentation Index
Fetch the complete documentation index at: https://mintlify.com/NVIDIA/NemoClaw/llms.txt
Use this file to discover all available pages before exploring further.
Inference profiles
NemoClaw ships with inference profiles defined inblueprint.yaml. Each profile configures an OpenShell inference provider and model route. The agent inside the sandbox uses whichever provider and model is active. Inference requests are routed transparently through the OpenShell gateway — they never leave the sandbox directly.
Two setup paths, two provider names. When using
openclaw nemoclaw launch or openclaw nemoclaw migrate, the blueprint creates providers with the names in the table below (for example, nvidia-inference). When using the standalone nemoclaw onboard wizard, the provider is named nvidia-nim instead. The provider name matters when running openshell inference set to switch models.Profile summary
| Profile | Provider name | Model | Endpoint | Notes |
|---|---|---|---|---|
default | nvidia-inference | nvidia/nemotron-3-super-120b-a12b | integrate.api.nvidia.com | Production. Requires NVIDIA API key. |
ncp | nvidia-ncp | nvidia/nemotron-3-super-120b-a12b | Configurable | NCP partner endpoint. Requires NVIDIA API key. |
nim-local | nim-local | nvidia/nemotron-3-super-120b-a12b | nim-service.local:8000 | Experimental. Requires NIM API key. |
vllm | vllm-local | nvidia/nemotron-3-nano-30b-a3b | localhost:8000 | Experimental. No API key required. |
Available models
Thenvidia-inference provider registers the following models from build.nvidia.com:
| Model ID | Label | Context window | Max output |
|---|---|---|---|
nvidia/nemotron-3-super-120b-a12b | Nemotron 3 Super 120B | 131,072 | 8,192 |
nvidia/llama-3.1-nemotron-ultra-253b-v1 | Nemotron Ultra 253B | 131,072 | 4,096 |
nvidia/llama-3.3-nemotron-super-49b-v1.5 | Nemotron Super 49B v1.5 | 131,072 | 4,096 |
nvidia/nemotron-3-nano-30b-a3b | Nemotron 3 Nano 30B | 131,072 | 4,096 |
default profile activates Nemotron 3 Super 120B. You can switch to any model in the catalog at runtime without restarting the sandbox.
Provider types
- NVIDIA Build (default)
- NCP partner
- Local NIM (experimental)
- vLLM (experimental)
- Ollama (experimental)
- Custom (experimental)
The default profile routes inference to NVIDIA’s hosted API at build.nvidia.com. This is the recommended option for most users — it requires no local infrastructure.Profile:
Getting an API key:Switch model at runtime:The change takes effect immediately. No sandbox restart is needed.
default| Field | Value |
|---|---|
| Provider name | nvidia-inference |
| Provider type | nvidia |
| Endpoint | https://integrate.api.nvidia.com/v1 |
| Default model | nvidia/nemotron-3-super-120b-a12b |
| Credential env | NVIDIA_API_KEY |
- Go to build.nvidia.com and sign in.
- Navigate to Settings → API Keys.
- Create a new key and copy it.
- Pass it to
openclaw nemoclaw onboard --api-key <key>or setNVIDIA_API_KEYin your environment.
~/.nemoclaw/credentials.json (mode 600).Onboard:Enabling experimental providers
Local inference options (NIM, vLLM, Ollama, custom) are hidden by default. Set theNEMOCLAW_EXPERIMENTAL environment variable to expose them in the interactive menu:
--endpoint directly without the environment variable — NemoClaw will issue a warning but proceed:
Credentials
Credentials are stored in~/.nemoclaw/credentials.json with file permissions set to 600. The credential environment variable used depends on the endpoint type:
| Endpoint type | Credential env |
|---|---|
build | NVIDIA_API_KEY |
ncp | NVIDIA_API_KEY |
custom | NVIDIA_API_KEY |
nim-local | NIM_API_KEY |
vllm | OPENAI_API_KEY (default: dummy) |
ollama | OPENAI_API_KEY (default: ollama) |
Switching models at runtime
After the sandbox is running, switch the active model with the OpenShell CLI. The provider name depends on the setup method used:- Plugin setup (openclaw nemoclaw)
- Standalone setup (nemoclaw onboard)
The blueprint creates a provider named
nvidia-inference: