Sora
For public Crazyrouter docs, the recommended verified Sora routes are:POST /v1/video/createwithGET /v1/video/queryPOST /v1/video/generationswithGET /v1/video/generations/{task_id}POST /v1/videoswithGET /v1/videos/{task_id}
POST /v1/video/generations. It has clearer task-state fields and is now documented in dedicated route pages as part of this update round.
Model Selection
| Model | Description | Speed | Quality | Recommended Use |
|---|---|---|---|---|
sora-2 | Second-generation standard model | Medium | High | Production and day-to-day usage |
sora-2-pro | Second-generation professional model | Slower | Highest | Professional work and finer control |
Recommended Main Path: Video Generations API
cURL
cURL
When to use this route
- first-pass Sora integration
- clearer task status and metadata
- teams that want to follow the new dedicated Crazyrouter video compatibility pages
Unified Video API
cURL
cURL
OpenAI-Compatible Video Format
cURL
cURL
Status And Result Fields
Common task states:| Status | Meaning |
|---|---|
queued | Submitted and waiting |
in_progress | Generating |
completed | Finished |
failed | Failed |
urlorvideo_url: video download URLthumbnail_url: preview thumbnailprogress: generation progressexpires_at: expiration time for the temporary result URL
Result URLs are usually not permanent. Download the video promptly instead of treating the returned URL as long-term storage.
Recommended Rollout Order
- Start with
sora-2 - Start with a short 5-10 second video
- Validate one simple text-to-video request first
- Add higher resolution, longer duration, or more advanced parameters later
- Switch to
sora-2-proonly after the basic path is stable
Practical Notes
- Do not assume every more complex native field is part of the stable public baseline
- If you need route-specific
Video Generationsexamples, prefer the new dedicated pages added in this docs round - If you are only checking connectivity, validate with a short prompt and short duration first
This page keeps the public Sora overview concise. More specific compatibility-route details have been split into dedicated video docs so each route can be maintained more accurately.