
Choose between the two currently advertised API video tiers, 768P and 2K, according to the delivery requirement and generation budget. 1K is an image tier but is not accepted by this video endpoint. Selecting 2K requests that tier; it is not a substitute for checking the delivered file or the quality of its motion.
Key takeaways
- Video currently costs 15 points per generated second at 768P or 30 at 2K.
- Increasing resolution does not guarantee correct faces, text, action or continuity.
- Compare candidate files at the intended display size before deciding whether a higher tier is worthwhile.
Fix the delivery requirement first
Decide where the clip will appear and how viewers will see its important details. A small preview tile and a large presentation screen can have different requirements. Neither the filename nor the API parameter alone proves that a clip meets them.
Use the current model hub for supported tiers and the API integration guide for exact field names. The request uses resolution, with 768P or 2K; it does not use an image-style size field or an arbitrary dimension string.
Compare the generation budget directly
These examples use the current rates with context_ir disabled. They count the requested generation duration, not a shorter excerpt you might keep after editing:
| Requested duration | 768P points | 2K points |
|---|---|---|
| 4 seconds | 60 | 120 |
| 8 seconds | 120 | 240 |
| 15 seconds | 225 | 450 |
Enhancement, if enabled, adds another five points to each video task. A separately generated reference image has its own image cost. Active membership is also required; the figures are not an offer to unlock API access by buying a particular points pack.
Keep the duration and tier together in the user's confirmation screen. A user who approves a four-second preview has not necessarily approved a fifteen-second 2K retake. The points and resolution guide provides the broader account-budget context.
Separate missing pixels from a wrong scene
A higher tier may be relevant when a composition is sound but the delivered detail is inadequate for its display size. It does not repair a missing object, a distorted hand or the wrong camera action simply by changing a parameter.
Pause the clip at a meaningful moment and write down the actual defect. Compare the saved file, not a compressed messaging preview or an aggressively cropped website card. For an existing soft clip, the upscale-or-regenerate guide helps distinguish a delivery transformation from a new generation decision.
Inspect the downloaded candidate
An application should record the requested tier and inspect the actual media metadata after download. If FFmpeg tools are installed in your own environment, this read-only ffprobe example shows selected stream and duration information:
ffprobe -v error -select_streams v:0 \
-show_entries stream=width,height,r_frame_rate:format=duration \
-of json candidate.mp4
The options are documented in FFmpeg's ffprobe reference. This is an external inspection tool, not an Imagild endpoint, and the command is an example rather than a report of a measured output. Use the returned metadata alongside full visual playback; dimensions alone do not establish acceptable detail.
Make a higher-tier retake a new decision
If you change a submitted request from 768P to 2K, create a new operation ID. It is a new generation with a different cost, not an identical retry. Keep the earlier result and request record so you can make a fair, documented comparison.
If a request is merely interrupted and its parameters remain identical, preserve its original idempotency key. If the task reports unknown, do not generate again just to discover whether the earlier request worked. Reconcile the original task first. Pass the selected tier only after the saved file satisfies the required crop, playback, detail and motion, without claiming that a single comparison establishes a universal quality ranking.
Related tasks
- Imagild Points, Resolution and Jobs: Plan a Creation Before You Spend
- Should I Upscale a Soft AI Video or Generate the Shot Again?
Sources and scope
- Imagild API integration guide: Actual request structure, references, task lifecycle, access conditions and retry behavior.
- Imagild model hub: Current video tiers, ratios, duration bounds and points.
- FFmpeg ffprobe documentation: External read-only media inspection and show_entries output; not a measured Imagild generation result.
Product instructions were checked against the current Imagild API contract and the public model catalog. Code, budgets and acceptance checks are illustrative; this article does not claim a new paid generation test, an uptime measurement, a search-volume study or a ranking of AI citations.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Original Imagild product screenshot captured on 28 October 2026; model availability and prices may change. This image is not an API response or a performance benchmark.