romtuck/openclaw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
92697edb7c
openclaw/docs/providers/zai.md
Jon Shapiro 92697edb7c fix(venice): add compat settings to prevent HTTP 400 errors 
Venice's API doesn't support certain OpenAI-compatible parameters that
Clawdbot sends by default:

- `store`: Venice returns HTTP 400 with no body when this is present
- `developer` role: Not supported by Venice's API

This adds VENICE_COMPAT settings (supportsStore: false,
supportsDeveloperRole: false) to all Venice model definitions, both
from the static catalog and dynamically discovered models.

Fixes issues reported in PR #1666 where users experienced silent
failures (HTTP 400, no body) when using Venice models.

Co-authored-by: jonisjongithub <jonisjongithub@users.noreply.github.com>
Co-authored-by: Clawdbot <bot@clawd.bot>
2026-01-26 17:56:01 -08:00

829 B
Raw Blame History

summary read_when
Use Z.AI (GLM models) with Clawdbot
You want Z.AI / GLM models in Clawdbot
You need a simple ZAI_API_KEY setup

Z.AI

Z.AI is the API platform for GLM models. It provides REST APIs for GLM and uses API keys for authentication. Create your API key in the Z.AI console. Clawdbot uses the zai provider with a Z.AI API key.

CLI setup

clawdbot onboard --auth-choice zai-api-key
# or non-interactive
clawdbot onboard --zai-api-key "$ZAI_API_KEY"

Config snippet

{
  env: { ZAI_API_KEY: "sk-..." },
  agents: { defaults: { model: { primary: "zai/glm-4.7" } } }
}

Notes

  • GLM models are available as zai/<model> (example: zai/glm-4.7).
  • See /providers/glm for the model family overview.
  • Z.AI uses Bearer auth with your API key.