Video
Video generation and video understanding: long-running work, results retrieved by id.
Note
The job routes are not built yet: POST /v1/jobs and GET /v1/jobs/{id} answer 404 route_not_found, so the asynchronous path this guide names is not available until they are (Jobs).
| Task | Path | Mode |
|---|---|---|
video_generation | Task API | Asynchronous only, on POST /v1/jobs. |
- Task
video_generation- Path
- Task API
- Mode
- Asynchronous only, on
POST /v1/jobs.
modelordeployment;task: "video_generation";inputsandoptionsas the model exposes them: duration, resolution, frame rate, number of outputs.- The job answers 202 at once with the job object; poll
GET /v1/jobs/{id}or use the SDK's wait helper. Cancel withPOST /v1/jobs/{id}/cancel.
per_second: per second of output video at a stated resolution and frame rate. Duration, resolution, frame rate and the number of outputs change the charge.
result.outputswith a presigned GET per output, retrievable untilexpires_atNot decided yet; the job record and its usage stay. Every status transition carries a timestamp and, when the scheduler has one, an explanation.
Note
Every number a task guide needs (limits, durations, dimension bands) is set per model in the catalog and is not written here. The SDK guide of the same task follows once the SDK's package names are decided Not decided yet.
Related sheets
- Sheet
- 06 of 20
- Detail
- E
- Updated
- 2026-11-11