minimax-hailuo-video

What it does

Build a reviewed request, obtain exact cost approval, create at most one paid task, then preserve the result and its evidence. Treat documentation gaps as unknowns, not defaults.

How it works

• Start with a boundary by selecting one service region and keeping account details, key, billing, host, and terms together for Global or Mainland China.
• Route by mode using POST /v1/video_generation for four modes (Text-to-video, Image-to-video, First/last frame, Subject reference) with specified required media and models.
• Build a request dossier before calling create, recording region, account identifiers, key type, model, mode, resolution, duration, currency, unit price, pricing-page retrieval time, exact prompt and parameters, source file metadata, audience, jurisdiction, disclosure plan, retention class, and attempt ID.
• Use specific image input constraints for first/last-frame and I2V modes; ensure aspect/resolution rules match mode requirements.
• Write prompts for the motion system following a defined compact order and ensure prompts respect mode constraints and optional fields like prompt_optimizer and fast_pretreatment.
• Make the paid boundary explicit: perform a dry-run, show redacted request, exact one-video cost, pricing timestamp, hashes, and host policy; require human digest approval and a positive maximum in the same currency.
• Before POSTing, acquire an exclusive ledger entry; after a response, keep an allowlisted summary only (task ID, provider code, status digest, timestamps).
• Follow retry and polling guidance, with explicit handling for various error codes and 5xx cases; do not assume success from HTTP alone.
• The Python 3.11+ client hailuo_generate.py is provided for dry-run behavior, detailing hosts, prices, models, and payment rules.

When to use it

Use when designing, implementing, debugging, or evaluating direct MiniMax/Hailuo video-generation API workflows. Do not use for consumer Hailuo site or unrelated MiniMax modalities.

What it can touch

• Tools declared: claude-code, codex, copilot, cursor. (Only listed tools are allowed.)

Caveats

• License: MIT
• Regions have separate service endpoints and currencies; a key/plan may not work across regions; do not translate prices between currencies.
• Restrictions on models and modes; some inputs and outputs are region/model dependent; verify availability and price in the correct console before paid use.
• Documentation gaps should be treated as unknowns, not defaults; no guarantees on endpoints beyond documented behavior.