Skip to main content
Create an API key in the developer console and choose a model from the catalog. Make the key available as NITO_API_KEY to the OpenClaw gateway process. An environment variable exported in an unrelated terminal will not reach an already running gateway service.

​
Configure the provider

In ~/.openclaw/openclaw.json, add a custom provider and select one of its models:
The nito/ prefix identifies OpenClaw’s provider. Nito receives moonshotai/kimi-k3. For another model, update both the provider’s models list and agents.defaults.model.primary using the exact catalog ID. Add a :confidential variant as a separate model entry when you want Confidential inference.

​
Check the route

Restart the managed gateway and inspect the resolved model:
The status should show nito/moonshotai/kimi-k3 as the selected model. Send a short message, then a second message to check conversation continuation. OpenClaw runs its own agent and tools; Nito serves the model calls.

​
Troubleshooting

  • If the model is unknown, check the provider key nito, the models entry, and the agents.defaults.model.primary value. The latter includes nito/; the model entry does not.
  • If authorization fails, make NITO_API_KEY available to the gateway service and restart it. Check the key in the developer console.
  • If a model disappears from the Nito catalog, update the OpenClaw model entry and default together. OpenClaw’s configured list is separate from the live Nito catalog.
OpenClaw documents these fields in its custom provider configuration.