An old integration may continue to create videos even as a provider advertises more recent flagship models.
The historical endpoint still matters
Vidu 2.0 is a useful example: the documented reference-to-video request uses the literal model string `vidu2.0` and a four-second duration. The page lists 360p and 720p resolution options for that duration. A migration to a different Q family is therefore not simply a model-name substitution; duration, reference format and error behavior may change.
Define the actual production task
Four seconds is enough for a small product move, a short reaction or a single establishing action. It is usually not enough for a sequence of three sales claims. Compose an opening still with sufficient space around the subject and ask for one deliberate motion. For a short looping background, inspect the first and final frames for abrupt resets; for a speech clip, plan a dedicated dubbing stage rather than assuming reference-to-video supplies a licensed voice.
Track asynchronous state properly
The documented task system uses state values such as `created`, `queueing`, `processing`, `success` and `failed`, and provides a creation-query route. An ingestion service should treat a returned task ID as receipt of a request rather than proof of a completed deliverable. Use signed callbacks where documented, query the job state if a callback is missed, and avoid counting the same successful job twice. Store vendor asset links with their actual expiry rather than relying on a permanently available download.
Why migration needs validation
A project that has historically been rendered at 720p should retain its original media and request data; upscaling an old video does not make it native 1080p. Preserve the old selection rules for archived articles, and begin a separate Q3 or Q4 profile if a migration is approved. Never rewrite past output metadata with newer model capacities. A before/after editorial sample set, made with authorized inputs, is a more defensible quality check than marketing slogans.
Rights and costs remain separate
The API documentation describes operations, not a universal license to use third-party likenesses or an entitlement for every plan and country. These decisions need their own source. A 4-second job might cost more or less under newer tariffs; record the account billing page or invoice when it is actually available. No financial price is inferred from this historical capability record.
Relevant alternatives and trade-offs
When broader duration and more reference pictures matter, examine Vidu Q3 or a different verified model family. Keep the `vidu2.0` original identifier in every legacy record.