All Things OpenClawAll Things OpenClaw
CONFIG • OpenClaw quick fix
Featured: @openclaw

OpenClaw web search works free — add a key only when you need more.

OpenClaw now bundles Parallel as a `web_search` provider. If no other provider is configured, `parallel-free` can work without an account or API key; the paid `parallel` provider uses `PARALLEL_API_KEY` for higher limits and tuning. That makes setup easier, but it also means operators should know which provider is actually serving searches before debugging stale results, missing excerpts, or rate limits.

In simple words: Make a safe copy if the step could change your setup, try the smallest check, then confirm OpenClaw is back to normal before doing more. The source link and commands stay below for people who want the technical detail.

Checklist
Run one tiny `web_search` task after upgrading and record whether it works with no key; do not assume a missing API key is the problem until provider routing is checked.
If the free provider is enough, leave it key-free and document that `parallel-free` is expected for this install.
If you need higher limits or paid tuning, set `PARALLEL_API_KEY` in the Gateway environment — for a gateway install, use `~/.openclaw/.env` or the official configure flow.
Paid provider environment note
# Free provider: no key required.
# Paid provider: set in the Gateway environment, then restart through your normal supervisor.
PARALLEL_API_KEY=par_...
Pin `tools.web.search.provider` to `parallel-free` or `parallel` only when you want explicit routing; otherwise note which auto-detected provider OpenClaw selected.
Explicit provider config to review
{
  "tools": {
    "web": {
      "search": {
        "provider": "parallel-free"
      }
    }
  }
}
When a search result looks stale or irrelevant, retry with a fresh query and record provider/session details before blaming the model.
Success looks like
• Operators can distinguish a key-free `parallel-free` route from a paid `parallel` route before debugging search behavior.
• The Gateway environment holds the paid key only when the paid provider is intentional.
• Search issues are triaged as provider/routing/session problems before becoming broad config churn.

Source: OpenClaw Parallel search docs + v2026.6.5 release · link