romtuck/openclaw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
92697edb7c
openclaw/docs/providers/models.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

1.4 KiB
Raw Blame History

summary read_when
Model providers (LLMs) supported by Clawdbot
You want to choose a model provider
You want quick setup examples for LLM auth + model selection

Model Providers

Clawdbot can use many LLM providers. Pick one, authenticate, then set the default model as provider/model.

Highlight: Venius (Venice AI)

Venius is our recommended Venice AI setup for privacy-first inference with an option to use Opus for the hardest tasks.

  • Default: venice/llama-3.3-70b
  • Best overall: venice/claude-opus-45 (Opus remains the strongest)

See Venice AI.

Quick start (two steps)

  1. Authenticate with the provider (usually via clawdbot onboard).
  2. Set the default model:
{
  agents: { defaults: { model: { primary: "anthropic/claude-opus-4-5" } } }
}

Supported providers (starter set)

For the full provider catalog (xAI, Groq, Mistral, etc.) and advanced configuration, see Model providers.