#HTTP 400: Provider returned error

1 messages · Page 1 of 1 (latest)

keen verge
#

I've had my secondary agents using hunter-alpha no problem, but when I try to get the main agent to use it, I just keep getting HTTP 400: Provider returned error. Can never seem to find out what the error is even in logs. I can use openrouter/auto, but not openrouter/hunter-alpha. But it works fine on my second agent and subagents on the installation. Any ideas? I've had openclaw and claude have at it without success.

feral treeBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> âś… Mark Solution

quiet karmaBOT
#

A 400 from OpenRouter almost always has a useful JSON body (e.g. “context length exceeded”, “tools not supported”, “unsupported parameter …”) — OpenClaw just won’t always surface that unless you turn verbosity on.

Here’s the quickest way to make this actionable:

  1. What version?
    Run and paste:
openclaw --version
  1. Force OpenClaw to show the provider’s real error
    In the failing chat/session (on the main agent), send:
/verbose on

Then immediately retry the same /model openrouter/hunter-alpha + a trivial prompt.
With verbose enabled, OpenClaw should append the raw “provider returned error” detail it’s currently hiding.

#
  1. Check if it’s a context-size mismatch (common when “auto” works)
    In the same failing session, run:
/context detail

If your main agent’s session/system prompt is big, hunter-alpha may have a smaller context window than whatever openrouter/auto routes you to, so the main agent fails while your secondary agent (smaller context) succeeds.

Fast test:

/new openrouter/hunter-alpha

…and send “ping”. If that works, your old session context was simply too large → /compact or start fresh.

  1. Compare OpenRouter config between agents
    On main agent and on the secondary agent (where it works), run: