Build with Grok Imagine Video 1.0
Make your first request
Use your Sorceress API key on your server. The playground uses your signed-in account; your application uses the same model with an API key.
curl -X POST 'https://sorceress.games/api/v1/jobs' \
-H 'Authorization: Bearer $SORCERESS_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"model": "xai/grok-imagine-video",
"input": {
"duration": 5,
"resolution": "720p",
"aspect_ratio": "16:9",
"generation_mode": "i2v",
"prompt": "<prompt>"
}
}'Inputs & settings
promptstringRequiredDescribe what you would like to create.
durationintegerVideo length (1-15 seconds)
resolutionstringOutput video resolution
Options: 480p, 720p
aspect_ratiostringVideo aspect ratio (T2V mode)
Options: 16:9, 9:16, 1:1, 4:3, 3:4, 3:2, 2:3
generation_modestringOptions: i2v, t2v
image_urlsarrayUpload a file or enter one public HTTPS URL per line.
Full input schema
{
"required": [
"prompt"
],
"properties": {
"prompt": {
"type": "string",
"title": "Prompt",
"description": "Describe what you would like to create."
},
"duration": {
"type": "integer",
"title": "Duration (seconds)",
"default": 5,
"minimum": 1,
"maximum": 15,
"description": "Video length (1-15 seconds)"
},
"resolution": {
"type": "string",
"title": "Resolution",
"default": "720p",
"enum": [
"480p",
"720p"
],
"description": "Output video resolution"
},
"aspect_ratio": {
"type": "string",
"title": "Aspect Ratio",
"default": "16:9",
"enum": [
"16:9",
"9:16",
"1:1",
"4:3",
"3:4",
"3:2",
"2:3"
],
"description": "Video aspect ratio (T2V mode)"
},
"generation_mode": {
"type": "string",
"title": "Mode",
"enum": [
"i2v",
"t2v"
],
"default": "i2v"
},
"image_urls": {
"type": "array",
"title": "Reference images",
"items": {
"type": "string",
"format": "uri"
},
"maxItems": 1,
"description": "Upload a file or enter one public HTTPS URL per line."
}
}
}Results, saved runs & billing
Media requests return a job ID. Poll GET /api/v1/jobs/:id until it succeeds or fails; keep the same ID while it is processing. Long chat requests can also return a saved job to poll. Completed outputs are stored in your account, and successful work is billed using your model's current rates.
A multi-step workflow may include separately billed successful actions. If a connection drops, check your saved run before submitting it again.
