Skip to main content
Image and video models do not share one universal parameter schema. Query before use:

Parameter checklist

Same parameter names do not mean same enums. For example, resolution, quality, and mode may have different meanings across models.

Billing

The parameter response may contain billingMode, chargeModes, and model-declared request fields. Media models may charge per request, per image, per second, or by combined rules. Actual charges are also affected by the API Key group multiplier. Check model marketplace and console prices before submitting, and use request details and billing as the final reference after completion.

MOV and other output formats

Only request MOV or another specified format when explicitly supported by the model parameters. If the model only returns MP4, do not fake it by changing the file extension; use an appropriate transcoding tool after download if needed.

How to read the parameters interface

First request the full JSON; do not rely only on static screenshots in documentation:
Focus on model-declared request fields, types, enums, defaults, and billing information such as billingMode and chargeModes. Fields not returned by the parameters interface should not be assumed to be supported.

Resolution and aspect ratio

Resolution describes pixels or clarity tiers; aspect ratio describes width-to-height proportion. They cannot replace each other. For example, different models may support different pixel tiers for the same 16:9 ratio; the same resolution tier may also allow only certain aspect ratios. When validating, cover at least: default, minimum, maximum, landscape, portrait, and unsupported combinations. Record actual output width and height; do not trust file names alone.

Duration

Video duration may be a fixed enum, a range, or automatically determined by the model. Confirm whether the unit is seconds, frames, or another form, and check whether duration directly affects cost. Before requesting longer videos, first validate the prompt and camera motion with the shortest duration.

Watermark

Check whether the model provides watermark control, whether it is watermarked by default, and whether disabling it requires additional permissions. Even if the interface allows disabling, comply with material licensing, platform branding, and local regulatory requirements.

Bitrate

Most generation models may automatically determine bitrate. Only pass bitrate when it is explicitly listed in the parameters interface. When stable delivery specifications are needed, generate first, then transcode and verify quality, frame rate, and audio-video synchronization in your own media processing pipeline.

MP4 and MOV

Parameter test matrix

For each test case, record request ID, task ID, actual parameters, output media information, latency, and cost. This lets you judge whether “the API accepted the parameter” and “the result truly met requirements” are consistent. Next: Image generation, Image editing, Video tasks, Request reliability.