Skip to main content
The NagaAI provider plugin adds NagaAI to OpenClaw as the nagaai provider. It reads the NagaAI model catalog, so OpenClaw knows each model’s context window, image input, reasoning support and price. New models appear without a config change. The plugin is @nagaai/openclaw-provider on ClawHub, and its source is on GitHub.

​
Before you start

You need a NagaAI API key and OpenClaw 2026.11.2 or later.

​
Connect OpenClaw

1

Install the plugin

OpenClaw asks you to accept the plugin’s capabilities, then loads it on the next Gateway start.
2

Add your key

Run onboarding and pick NagaAI:
The plugin also reads the key from NAGA_API_KEY in the environment that runs the OpenClaw Gateway.
3

Pick a model

List the NagaAI models and set one as the default:
A model reference is nagaai/ followed by the NagaAI model id from /v1/models.

​
Requests and the model list

The plugin sends requests to the Responses API at https://api.naga.ac/v1. NagaAI keeps no conversation state, so OpenClaw sends the whole conversation on every turn, as it does for any Responses endpoint it doesn’t host. Chat Completions is there only for a proxy that can’t forward Responses: set plugins.entries.nagaai.config.api to the Chat Completions API in the OpenClaw config. The model list comes from the public GET /v1/models, without your key, and lists the chat models that take tools. The plugin caches it for a minute. /v1/models has no per-model output limit, so the plugin gives every model OpenClaw’s default of 8,192 output tokens. Raise it for one model with maxTokens in that model’s params under agents.defaults.models.

​
Troubleshooting

​
401 invalid_api_key

OpenClaw sends no key or a wrong one. Run onboarding again, or export NAGA_API_KEY in the environment that runs the OpenClaw Gateway.

​
400 model_not_found

The part after nagaai/ isn’t a NagaAI model id. Pick one from openclaw models list --provider nagaai --all.