Personal AI agent
How to Use Ruvicode with OpenClaw
OpenClaw reaches OpenAI-compatible APIs through custom providers under models.providers. This guide adds Ruvicode as one, reads the key from the environment, and makes a Ruvicode model the default.
Checked on November 3, 2026. Config checked against OpenClaw's configuration and custom provider documentation. The requests OpenClaw sends with api openai-completions, streamed chat completions with tool calls, completed through api.ruvicode.com.
Set up OpenClaw
Base URL
https://api.ruvicode.com/v1
API key
rvcd_...
- 1Export RUVICODE_API_KEY=rvcd_... in the environment OpenClaw runs in.
- 2Add the ruvicode provider below to ~/.openclaw/openclaw.json (JSON5, comments allowed). List each model you want with its context window and max output.
- 3Make one of them the default with openclaw models set ruvicode/glm-5.3-flash, then check the list with openclaw models list.
{
models: {
providers: {
ruvicode: {
baseUrl: "https://api.ruvicode.com/v1",
apiKey: "${RUVICODE_API_KEY}",
api: "openai-completions",
models: [
{ id: "glm-5.3-flash", name: "GLM 5.3 Flash", input: ["text"], contextWindow: 1000000, maxTokens: 128000 },
{ id: "claude-sonnet-5.5", name: "Claude Sonnet 5.5", input: ["text", "image"], contextWindow: 1000000, maxTokens: 128000 },
],
},
},
},
}openclaw models set ruvicode/glm-5.3-flash
openclaw models listGood to know
- Model refs in OpenClaw are provider/model, so a Ruvicode model is ruvicode/<model id>.
- Set input to ["text", "image"] only for vision models; OpenClaw reads it to decide whether a model can take image attachments.
- OpenClaw only allows model requests to the exact origin in baseUrl, so keep it at https://api.ruvicode.com/v1.
Models for coding agents
These models completed streamed tool calls through Ruvicode on November 3, 2026. Every model in the catalog works with the same base URL and key; each model page shows its live rate, context window and max output.
- GLM 5.3 Flash
glm-5.3-flash - Claude Sonnet 5.5
claude-sonnet-5.5 - Kimi K2.7 Code
kimi-k2.7-code
Common errors
- 401 Invalid API key
- The key is mistyped, revoked or not a Ruvicode key. Copy it again from the dashboard; it starts with rvcd_.
- 404 Model not found
- The model id is not in the catalog. Use an id exactly as listed on the models page or by GET /v1/models. A plain 404 page instead of a JSON error means the base URL is missing /v1.
- 402 insufficient_balance
- The wallet cannot cover the request. Top up in the dashboard; the balance never expires.
- 429 rate limit
- Too many requests per minute, on the key or across the account. Agents that fire many calls in parallel can hit it; most tools retry on their own after a short wait.
OpenClaw with Ruvicode: FAQ
- Which api value should I use for Ruvicode in OpenClaw?
- openai-completions, which is also OpenClaw's default when a provider has a baseUrl and no api. Ruvicode serves chat completions, not the Responses API, so do not use openai-responses.
- Can I keep my other OpenClaw providers?
- Yes. models.providers merges with OpenClaw's built-in providers by default, so Ruvicode sits next to them and you switch with openclaw models set.
- Where do I get a Ruvicode API key?
- Create an account, top up your wallet with QRIS or USDC, then open API Keys in the dashboard and create a key. Keys start with rvcd_. You can set a daily or monthly spend limit per key and restrict a key to a list of models.
Guides for other tools
The same base URL and key work everywhere. Setup for each tool: