openclaw - 💡(How to fix) Fix MiniMax Token Plan support gaps: video_generate rejects 768P and music provider defaults to unsupported music-2.5+ [1 comments, 1 participants]

Summary

OpenClaw 2026.4.5 does not correctly match MiniMax Token Plan behavior for video and music generation on the CN endpoint.

MiniMax Token Plan docs: https://platform.minimaxi.com/docs/token-plan/intro

Environment

• OpenClaw: 2026.4.5
• MiniMax CN endpoint: https://api.minimaxi.com
• Token Plan includes:
  • MiniMax-M2.7-highspeed
  • Speech 2.8
  • image-01
  • Hailuo-2.3-Fast-768P 6s
  • Hailuo-2.3-768P 6s
  • music-2.5

Problem 1: video_generate rejects 768P before request is sent

Repro

Ask an agent to call video_generate with:

• model: default MiniMax video model (MiniMax-Hailuo-2.3)
• resolution: 768P
• duration: 6

Actual result

OpenClaw rejects the request locally with:

resolution must be one of 480P, 720P, or 1080P

Expected result

768P should be accepted for MiniMax Token Plan usage.

Evidence

Direct call to MiniMax CN API succeeds:

curl -H 'Authorization: Bearer ...'   -H 'Content-Type: application/json'   -d '{"model":"MiniMax-Hailuo-2.3","prompt":"a ginger cat watching rain","resolution":"768P","duration":6}'   https://api.minimaxi.com/v1/video_generation

Response:

{"task_id":"...","base_resp":{"status_code":0,"status_msg":"success"}}

Additional evidence

MiniMax-Hailuo-2.3-Fast correctly returns:

invalid params, model MiniMax-Hailuo-2.3-Fast does not support Text-to-Video mode

So the main issue is not the account; the main issue is local 768P validation blocking a valid request for MiniMax-Hailuo-2.3.

Problem 2: MiniMax music defaults are mismatched for Token Plan

Actual OpenClaw behavior

MiniMax music provider default model is music-2.5+.

Actual Token Plan behavior

Direct MiniMax API returns:

your current token plan not support model, music-2.5+

for music-2.5+.

But music-2.5 is included in Token Plan.

Additional API behavior

Direct MiniMax API returns:

invalid params, lyrics is required

when calling music-2.5 without lyrics.

Direct MiniMax API also returns:

invalid params, is_instrumental only supported on music-2.5+

when is_instrumental is used with music-2.5.

Expected result

For Token Plan compatibility, OpenClaw should at least:

• default MiniMax music model to music-2.5 when that is the only supported model
• not assume music-2.5+ is available
• avoid sending is_instrumental for music-2.5
• require or help supply lyrics for music-2.5

Suspected root causes

1. video_generate tool schema / normalization only accepts 480P | 720P | 1080P, which is too narrow for MiniMax Token Plan.
2. MiniMax music provider defaults are written for music-2.5+ behavior, but Token Plan access is music-2.5.

Why this matters

MiniMax Token Plan is advertised as supporting these media capabilities, but OpenClaw currently makes valid Token Plan use cases fail locally or use the wrong model defaults.