InferenceManage Inference

View the Selected Inference Path

View as Markdown

Use the NemoClaw CLI to read the selected inference provider and model. When the selected sandbox has a valid native NVIDIA provider attachment, the command reports the sandbox’s recorded provider, model, and fixed NVIDIA endpoint without reading the shared gateway route. For other providers, the command reads the live OpenShell inference route. For a compatible custom provider, the command also reports its persisted endpoint URL when the registry provider and model match the live route. This command reports configuration state and does not authenticate a model request.

Read the Selected Inference Path

Run the direct route command when you need the active provider, model, and applicable custom endpoint URL. The direct form first checks the default sandbox in the registry that NEMOCLAW_GATEWAY_PORT selects. It reports that sandbox’s native NVIDIA provider path when a valid attachment exists. Otherwise, it reads the gateway that NEMOCLAW_GATEWAY_PORT selects.

nemo-deepagents inference get

Expected output:

Provider: nvidia-prod
Model:    nvidia/nemotron-3-super-120b-a12b
Endpoint: https://integrate.api.nvidia.com/v1

Pass --json for machine-readable output.

nemo-deepagents inference get --json

Expected output:

{
  "provider": "nvidia-prod",
  "model": "nvidia/nemotron-3-super-120b-a12b",
  "endpointUrl": "https://integrate.api.nvidia.com/v1"
}

For compatible-endpoint and compatible-anthropic-endpoint, the text output adds Endpoint only when every matching published registry row records the live provider and model. Those rows must also agree on one API family, credential identity, and canonical, credential-free, reusable HTTP(S) URL. The URL must use the documented root or /v1 API-base path; NemoClaw omits other paths because an opaque segment can carry a credential. The JSON output adds endpointUrl under the same condition. For example:

Provider: compatible-endpoint
Model:    custom-model
Endpoint: https://inference.example.com/v1
{
  "provider": "compatible-endpoint",
  "model": "custom-model",
  "endpointUrl": "https://inference.example.com/v1"
}

A valid native NVIDIA attachment adds the fixed NVIDIA endpoint to the provider-and-model output. Other managed providers keep the provider-and-model output. Unpublished sandbox rows do not participate in endpoint selection. Equivalent stored URL forms, such as a trailing slash difference, count as the same endpoint identity. NemoClaw omits the endpoint when participating registry metadata is absent, conflicting, invalid, too long, uses another path shape, or contains userinfo, a query, a fragment, control characters, or recognized credential material in any URL component. It also omits an internal HTTPS-pin adapter route because the upstream endpoint is intentionally not retained and the adapter URL cannot be reused as an upstream endpoint. When a compatible endpoint is omitted, text output reports Endpoint: unavailable (<state>) followed by a credential-free Action. JSON output adds endpointStatus and endpointRecovery instead of endpointUrl. The state is unavailable when durable registry metadata cannot be found or an unclassified registry read fails, registry-corrupt when the sandbox registry is not valid JSON, registry-unreadable when NemoClaw cannot read the registry because of its ownership or permissions, invalid when recorded metadata or URL validation cannot prove the live route, conflicting when eligible same-gateway rows disagree on endpoint, API family, or credential identity, withheld when a syntactically valid URL has an opaque path or recognized credential material that NemoClaw does not display, and adapter-managed for an internal HTTPS-pin adapter route. For invalid and conflicting, JSON also returns up to eight output-safe names in affectedSandboxes; text output prints the same names after Affected. When more output-safe names exist, JSON sets affectedSandboxesTruncated to true and text output says that additional names are not shown. The recovery action tells you to restore registry access, restore a known-good registry backup or obtain recovery support, repair state-directory ownership or permissions, repair the named registrations and rerun the command for another affected batch, align conflicting routes, use a credential-free root or /v1 API base, or omit endpoint options for an adapter-managed same-provider model change. These endpoint-omission fields never include a stored URL, registry path, or underlying registry error. If a sandbox-first lookup cannot resolve its gateway because the registry is corrupt or unreadable, the command exits non-zero and retains the safe recovery steps and affected path. If the requested sandbox has an invalid gateway binding, the error names that sandbox and tells you to repair or remove its registration without displaying the rejected gateway value or port.

A shared-route lookup exits non-zero with OpenShell inference route is not configured for gateway '<gateway-name>'. when the selected gateway has no configured inference route. Run nemo-deepagents onboard to configure one. For lookup failures, the error names the gateway without rendering command output. It reports a timeout, a nonzero exit status, no exit status, or output NemoClaw cannot interpret after a command exits successfully. Run nemo-deepagents status after a direct lookup fails. Run nemo-deepagents <name> status after a sandbox-first lookup fails.

Use the Sandbox-First Form

Use the sandbox-first form when you are already working with a named sandbox.

nemo-deepagents <name> inference get

NEMOCLAW_GATEWAY_PORT first selects the sandbox registry and fallback gateway. When the named sandbox has a valid native NVIDIA provider attachment, the command reports its recorded provider, model, and fixed NVIDIA endpoint without reading the shared gateway route. Otherwise, when that registry contains the named sandbox, the command resolves its recorded gateway and reads that gateway-wide route. For a compatible custom provider, the command reports an endpoint only when every eligible published row on the resolved gateway matches the live route and records the same safe, reusable endpoint. The command does not search registries for other gateway ports. For other providers, OpenShell exposes one inference route to every sandbox registered on the same gateway.

Include Sandbox Health

Run the sandbox status command when you also need service, messaging, and inference health.

nemo-deepagents <name> status

The status output shows the provider and model recorded for that sandbox. When the gateway’s live shared route differs, status prints both routes and reports whether connect can safely restore the recorded route. Refer to Use Shared Gateway Routes for the text and JSON drift fields and their compatibility rules. Use the route verification workflow when you need to prove that an inference request succeeds through the sandbox path.