CCAPI Developer Platform

MiniMax H3 API

Integrate MiniMax H3 through CCAPI’s unified video API platform.

What MiniMax H3 does

Use one API for 5–15 second H3 Max Turbo and H3 text-to-video, image-to-video, and multimodal reference-to-video. H3 reference mode accepts images, videos, and audio and covers video-to-video editing.

  • Natural Motion with Frame Constraints — Upload one image to anchor the opening composition, or add a second image to define the final frame. The model fills the interval with subject motion, camera travel, and evolving light while respecting those visual anchors.
  • From Fast Previews to High-Resolution Delivery — Validate motion at 480P or 768P, then move to 1080P, 2K, or 4K where the selected model supports it. The same task contract carries previews and final renders through one polling and result-handling flow.

MiniMax H3 API features

  • Two Model Variants — H3 Max Turbo emphasizes detailed motion, while H3 supports output up to 4K.
  • First and Last Frame Control — Provide up to two images to define the opening and ending compositions.
  • 5–15 Second Output — Select duration in seconds for ad shots, product animation, and concept clips.
  • Repeatable Generations — Control randomness with seed and configure safety checking and prompt expansion.

What people build with MiniMax H3

  • Product Shots — Turn a product still into rotations, push-ins, and detail reveals while keeping the composition stable.
  • Advertising Storyboards — Define transition intent with opening and ending frames to validate shot rhythm and visual direction quickly.
  • Social Clips — Generate compact source clips for social formats, then assemble and score them in the editing workflow.
  • Concept Visualization — Translate atmosphere, character action, and cinematography language into reviewable motion concepts.

Getting started with the MiniMax H3 API

The endpoint is OpenAI-compatible, so existing client code usually needs only a base URL and a model name.

  • Step 1: Create an API Token — Create a token in the console for Bearer authentication.
  • Step 2: Choose Model and Tier — Choose a canonical model ID, then set duration and a supported resolution.
  • Step 3: Submit the Task — Send the prompt to POST /v1/videos with optional opening and ending frames.
  • Step 4: Poll and Save the Result — Poll by task ID, then read metadata.url and save the completed video.

MiniMax H3 API pricing

5s H3 Max Turbo at 768P: $0.24

MiniMax H3 Family Pricing
Model480P per second768P per second1080P per second2K per second4K per second
H3 Max Turbo$0.030/s$0.048/s$0.096/s--
H3$0.060/s$0.072/s-$0.156/s$0.192/s

Why choose CCAPI for MiniMax H3

  • One Task Contract — Both models share submission, polling, and result shapes, so switching variants does not require a new task pipeline.
  • Published Per-Second Pricing — Per-second rates are listed by model and resolution so the application can calculate budget before submission.
  • Practical Generation Controls — The API exposes duration, resolution, seed, safety checking, and prompt expansion controls needed in production.

Other models on the same endpoint

The same API key and base URL reach every model below. Moving from MiniMax H3 to any of them means changing the model name in the request body.

Frequently asked questions

How do H3 Max Turbo and H3 differ?

H3 Max Turbo targets detailed motion at 480P, 768P, or 1080P. H3 supports 480P, 768P, 2K, and 4K.

How much does a 5-second video cost?

H3 Max Turbo at 768P is $0.24 and H3 at 768P is $0.36. For other tiers, multiply the listed per-second rate by five.

How do I provide opening and ending frames?

Pass image URLs in the images array. The first becomes the opening frame and the second the ending frame; one image creates a first-frame animation.

How do I run video-to-video?

Use minimax/h3/reference-to-video and pass up to three video URLs in metadata.reference_video_urls. You can also include up to nine reference images and three audio URLs.

Is the API asynchronous?

Yes. POST /v1/videos returns a task_id. Poll GET /v1/videos/{task_id}, then read the completed video URL from metadata.url.