
Require an explicit application approval tied to the exact source image and planned video request before submitting the video. A successful image task is a technical prerequisite, not a user's consent to spend on the next stage. Imagild accepts the child video as a separate paid operation, so your application must enforce its own review gate.
Key Takeaways
- Bind approval to the source task and the full child-request snapshot.
- Changes to prompt, model settings, duration, or source require a fresh review.
- Duplicate clicks after approval should recover one child operation rather than create additional videos.
Present the decision the user is actually making
After the image succeeds, show the approved source through authorized media delivery. Let the reviewer inspect composition, subject details, text, and suitability for the intended motion.
The first-frame motion guide helps evaluate whether a still supports the requested action. A visually attractive image may still be unsuitable as a moving shot's starting point.
Do not submit a video automatically merely because the image status changes to succeeded. The API console exposes generation endpoints, not an Imagild approval API; this gate is part of your product.
Put source, settings, and cost on one review card
For an illustrative blue-boat shot, a review card could show:
| Review item | Planned value |
|---|---|
| Source | Completed owned image task with visible preview |
| Motion prompt | Boat drifts slowly; overhead camera remains steady |
| Model | MiniMax-H3 |
| Duration and resolution | 4 seconds, 768P |
| Aspect ratio and role | 16:9, first frame |
| Context IR | Disabled |
| Child generation quote | 60 points |
If the image was separately generated at 1K, its 10-point cost is separate; the simple image-plus-video plan allocates 70 points. Check current offers in the model market. API access requires active membership independently of points.
Do not describe this quote as unlimited retakes or a guarantee of perfect motion.
Bind approval to a versioned request
Store an application approval record containing the authorized reviewer, source task ID, optional verified source checksum, complete child payload snapshot, displayed quote, and approval timestamp.
Use a revision or fingerprint to detect changes. If the user changes four seconds to eight, selects another source, or edits the prompt, the prior approval must not authorize that altered request automatically.
Approval metadata stays in your database. The child generation body contains only supported video fields, including the owned image_task_id; do not add approved_by, approval_id, or template metadata to strict API JSON.
The same approved source can feed a video without your application inventing a public image URL. Source availability and ownership are still validated when the child is submitted.
Enforce the gate on the server
A disabled browser button is not an authorization boundary. Your backend should verify the application user's access, source readiness, current plan revision, approval state, and allowed budget before dispatch.
OWASP's REST guidance supports authorization and input validation at protected operations. An approved browser label alone is not enough.
Persist one child operation key before sending the request. Repeated activation of that approved action must reuse the same saved key and parsed parameters. If acknowledgment is lost, recover that operation instead of treating the approval as permission for a fresh paid attempt.
Test review changes and failure branches
Use fixtures to check these conditions: source still waiting, source failed, source succeeded but unapproved, exact plan approved, plan edited after approval, duplicate dispatch, and source unavailable at submission.
The first three must not submit a child. Editing should return the plan to review. Duplicate dispatch should preserve identity. A missing source should produce a specific correction rather than a text-only fallback video.
After a successful child, review the clip before publication. If it fails or becomes unknown, use the failed-job guide to choose recovery. A human review gate keeps technical completion, creative acceptance, and additional spend as three explicit decisions.
Related tasks
- How Can My AI Clip Start in Motion Instead of Spending Seconds Accelerating?
- What Should You Check Before Retrying a Failed Image or Video Job?
Sources and scope
- Imagild API console: Video child is a separate paid async operation; completed owned image_task_id and strict fields.
- Imagild model market: 4sec768P60pointsIRoff, optional1Ksource10points example.
- OWASP REST Security Cheat Sheet: Server-side authorization and input validation cannot be replaced by browser UI state.
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.