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

959 B
Raw Blame History

summary read_when
Brave Search API setup for web_search
You want to use Brave Search for web_search
You need a BRAVE_API_KEY or plan details

Brave Search API

Clawdbot uses Brave Search as the default provider for web_search.

Get an API key

  1. Create a Brave Search API account at https://brave.com/search/api/
  2. In the dashboard, choose the Data for Search plan and generate an API key.
  3. Store the key in config (recommended) or set BRAVE_API_KEY in the Gateway environment.

Config example

{
  tools: {
    web: {
      search: {
        provider: "brave",
        apiKey: "BRAVE_API_KEY_HERE",
        maxResults: 5,
        timeoutSeconds: 30
      }
    }
  }
}

Notes

  • The Data for AI plan is not compatible with web_search.
  • Brave provides a free tier plus paid plans; check the Brave API portal for current limits.

See Web tools for the full web_search configuration.