Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Xiaomi MiMo API returns 400 Param Incorrect for mimo-v2.5 series

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

  1. Model Naming (Dot vs Hyphen): Xiaomi's V2.5 series uses dots (e.g., mimo-v2.5-pro). If the internal provider logic normalizes these dots into hyphens (mimo-v2-5-pro), the API rejects the request with a 400 error.
  2. Strict Parameter Filtering: Xiaomi's latest API update (May 2026) no longer ignores unknown parameters. Requests containing Anthropic-specific fields (like output_config) or OpenAI-specific extensions that are not supported by MiMo now trigger a hard 400 error.

Root Cause

Root Cause Analysis:

Based on logs and community findings, there are two primary suspects:

  1. Model Naming (Dot vs Hyphen): Xiaomi's V2.5 series uses dots (e.g., mimo-v2.5-pro). If the internal provider logic normalizes these dots into hyphens (mimo-v2-5-pro), the API rejects the request with a 400 error.
  2. Strict Parameter Filtering: Xiaomi's latest API update (May 2026) no longer ignores unknown parameters. Requests containing Anthropic-specific fields (like output_config) or OpenAI-specific extensions that are not supported by MiMo now trigger a hard 400 error.

Code Example

{
  "event": "model_fallback_decision",
  "requestedProvider": "xiaomi",
  "requestedModel": "mimo-v2.5-pro",
  "status": 400,
  "errorPreview": "400 Param Incorrect",
  "message": "LLM request failed: provider rejected the request schema or tool payload."
}
RAW_BUFFERClick to expand / collapse

Xiaomi MiMo API calls started failing recently (around mid-May 2026) with HTTP 400: Param Incorrect. This appears to be a regression or a strict change in Xiaomi's API validation.

Root Cause Analysis:

Based on logs and community findings, there are two primary suspects:

  1. Model Naming (Dot vs Hyphen): Xiaomi's V2.5 series uses dots (e.g., mimo-v2.5-pro). If the internal provider logic normalizes these dots into hyphens (mimo-v2-5-pro), the API rejects the request with a 400 error.
  2. Strict Parameter Filtering: Xiaomi's latest API update (May 2026) no longer ignores unknown parameters. Requests containing Anthropic-specific fields (like output_config) or OpenAI-specific extensions that are not supported by MiMo now trigger a hard 400 error.

Logs / Evidence:

{
  "event": "model_fallback_decision",
  "requestedProvider": "xiaomi",
  "requestedModel": "mimo-v2.5-pro",
  "status": 400,
  "errorPreview": "400 Param Incorrect",
  "message": "LLM request failed: provider rejected the request schema or tool payload."
}

Environment:

  • OpenClaw Version: 2026.5.12 (f066dd2)
  • Runtime: OpenClaw Pi Default
  • Affected Provider: xiaomi / mimo-direct

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#prompt template#agent execution#callback error#memory management

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Xiaomi MiMo API returns 400 Param Incorrect for mimo-v2.5 series