WAND-Vega-Video RTC โ
Real-time, fast video generation. WAND-Vega-Video RTC targets low-latency use cases: the sync endpoint usually returns the finished video in 5โ20 seconds, or you can submit through the async endpoint and poll.
| Item | Value |
|---|---|
| Domain | https://platform.wand-aigc.com |
| Model | wand-vega-video-1.0-rtc |
| Authentication | Request header X-Api-Key: <your_api_key> |
| Generation modes | Text-to-video, first/last-frame-to-video, reference-image-to-video |
1. Endpoints โ
| Method | Path | Purpose |
|---|---|---|
| POST | /v1/wand/vega-videos/generation/async | Submit a task and return task_id immediately (does not wait for generation) |
| POST | /v1/wand/vega-videos/generation/sync | Submit a task, wait until generation finishes and return the result directly (usually 5โ20 s) |
| GET | /v1/wand/vega-videos/tasks/{task_id} | Query task status and result |
async and sync take exactly the same request body; they differ only in when they return:
- async: returns
task_idright after submission while the task runs in the background. Poll the query endpoint withtask_id;statuschanges fromrunningtosucceededorfailed. - sync: waits until generation finishes and returns the final result โ no extra query needed (usually 5โ20 s; set the client timeout to 2 minutes or more).
WARNING
A successful async submission only means the task was accepted. Generation failures are not reflected in the submission response โ rely on the status in the query result.
2. Request Parameters โ
Top-level fields โ
| Field | Type | Required | Description |
|---|---|---|---|
model | string | Yes | Fixed: wand-vega-video-1.0-rtc |
content | array | Yes | Input content; at least one item, and at least one item must be a non-empty text |
resolution | string | Yes | 480P / 768P / 1080P |
duration | int | Yes | Duration in seconds, 4โ15 |
ratio | string | No | Aspect ratio, default adaptive; specifying it explicitly is recommended |
enable_ir | bool | No | Prompt optimization, default false |
ratio values โ
21:9, 16:9, 4:3, 1:1, 3:4, 9:16, adaptive
adaptive is ambiguous in some cases: it is not supported for pure text-to-video, and is treated as 16:9 for first/last-frame generation.
content[] items โ
| Field | Type | Description |
|---|---|---|
type | string | text / image_url |
text | string | Prompt when type = text; must not be empty |
image_url.url | string | Image URL when type = image_url; must be publicly accessible |
role | string | Image role, see the table below |
role โ
| role | Scenario | Description |
|---|---|---|
first_frame | Image-to-video | First-frame image |
last_frame | Image-to-video | Last-frame image; must be used together with first_frame |
reference_image | Image-to-video | Reference image |
Prompt optimization (enable_ir) โ
- Default
false: generate directly from thetextincontent; - Set to
true: the prompt is first rewritten, using the text and assets, into a structured description better suited to video generation, then generation starts.
3. Examples โ
Example 1: Text-to-video โ
curl -sS -X POST 'https://platform.wand-aigc.com/v1/wand/vega-videos/generation/async' \
-H 'Content-Type: application/json' \
-H 'X-Api-Key: <your_api_key>' \
-d '{
"model": "wand-vega-video-1.0-rtc",
"content": [
{"type": "text", "text": "A dog running on the grass"}
],
"resolution": "1080P",
"duration": 5,
"ratio": "16:9"
}'Response:
{"task_id": "251250701-AigcVideo-41793bd8ad67d1eef3bc1ff3247dac5d"}Example 2: First/last frame (image-to-video) โ
text + a first-frame image; to add a last frame, append another item with role: last_frame.
curl -sS -X POST 'https://platform.wand-aigc.com/v1/wand/vega-videos/generation/async' \
-H 'Content-Type: application/json' \
-H 'X-Api-Key: <your_api_key>' \
-d '{
"model": "wand-vega-video-1.0-rtc",
"content": [
{"type": "text", "text": "The camera slowly pushes in as the puppy turns to look at the lens"},
{"type": "image_url", "image_url": {"url": "https://example.com/dog.jpg"}, "role": "first_frame"}
],
"resolution": "480P",
"duration": 5,
"ratio": "16:9"
}'Example 3: Get the result in one call (sync) โ
curl -sS -X POST 'https://platform.wand-aigc.com/v1/wand/vega-videos/generation/sync' \
-H 'Content-Type: application/json' \
-H 'X-Api-Key: <your_api_key>' \
-d '{
"model": "wand-vega-video-1.0-rtc",
"content": [{"type": "text", "text": "A dog running on the grass"}],
"resolution": "480P",
"duration": 6,
"ratio": "1:1"
}'On success, the response body is identical to the query result in "4. Response Parameters"; on failure, an error envelope is returned (see "5. Error Codes").
Example 4: Poll the task (after async) โ
curl -sS 'https://platform.wand-aigc.com/v1/wand/vega-videos/tasks/251250701-AigcVideo-41793bd8ad67d1eef3bc1ff3247dac5d' \
-H 'X-Api-Key: <your_api_key>'While status is running, retry every 2โ5 seconds; stop once it becomes succeeded / failed.
Appendix: Enabling prompt optimization โ
{
"model": "wand-vega-video-1.0-rtc",
"content": [{"type": "text", "text": "cat in garden"}],
"enable_ir": true,
"resolution": "768P",
"duration": 5,
"ratio": "16:9"
}4. Response Parameters โ
Submission succeeded (async) โ
{"task_id": "251250701-AigcVideo-41793bd8ad67d1eef3bc1ff3247dac5d"}After getting task_id, poll the query endpoint; status changes from running to succeeded or failed (usually within 20 seconds).
Query result (GET) โ
A successful sync call returns exactly this structure. A failed sync call returns the error envelope directly (see "5. Error Codes") with the failure reason in Message; it does not return a task with status=failed.
Running:
{
"task": {
"id": "251250701-AigcVideo-41793bd8ad67d1eef3bc1ff3247dac5d",
"model": "wand-vega-video-1.0-rtc",
"status": "running",
"created_at": 1793168600,
"resolution": "480P",
"duration": 6,
"ratio": "1:1",
"content": {"url": ""}
}
}Succeeded:
{
"task": {
"id": "251250701-AigcVideo-41793bd8ad67d1eef3bc1ff3247dac5d",
"model": "wand-vega-video-1.0-rtc",
"status": "succeeded",
"created_at": 1793168600,
"resolution": "480P",
"duration": 6,
"ratio": "1:1",
"content": {
"url": "https://.../251250701-AigcVideo-41793bd8ad67d1eef3bc1ff3247dac5d.mp4?q-sign-time=..."
}
}
}Failed:
{
"task": {
"id": "251250701-AigcVideo-41793bd8ad67d1eef3bc1ff3247dac5d",
"model": "wand-vega-video-1.0-rtc",
"status": "failed",
"created_at": 1793168600,
"resolution": "480P",
"duration": 6,
"ratio": "1:1",
"content": {"url": ""},
"error": "generate failed"
}
}| Field | Type | Description |
|---|---|---|
task.id | string | Task ID, same as the task_id returned on submission |
task.model | string | Fixed: wand-vega-video-1.0-rtc |
task.status | string | running / succeeded / failed |
task.created_at | int | Creation time (Unix seconds) |
task.resolution | string | Resolution tier, same as submitted |
task.duration | int | Submitted duration (seconds) |
task.ratio | string | Aspect ratio |
task.content.url | string | Download URL of the video; only set on success, valid for 1 hour by default |
task.error | string | Failure reason; only set on failure, absent on success |
Fields not listed in the response can be ignored.
Response headers โ
X-Request-Id: request ID โ provide it when troubleshooting.
5. Error Codes โ
Error envelope:
{"Response":{"Error":{"Code":"...","Message":"..."},"RequestId":"..."}}| HTTP | Code | Meaning | Action |
|---|---|---|---|
| 401 | AuthFailure.MissingAuthorization | X-Api-Key missing | Add the request header |
| 401 | AuthFailure.InvalidAuthorization | Invalid key | Check the key |
| 400 | InvalidParameter | Invalid parameter | Fix the field according to Message |
| 400 | InvalidParameter.UnsupportedFeature | Uses a capability not yet supported (reference image / video / audio, asset transfer, callback_url, etc.) | Remove the field per Message, or switch to text-to-video / first/last frame |
| 403 | UnauthorizedOperation.AppidNotAllowed | Account not enabled | Contact us to enable |
| 429 | LimitExceeded | Too many requests, or the concurrent task limit is reached | Retry later |
| 404 | ResourceNotFound.TaskId | Task does not exist or does not belong to this account | Check task_id |
| 502 | FailedOperation.VendorError | Generation failed | Retry later |
| 503 | ResourceUnavailable.NoAvailableAccount | Service resources temporarily insufficient | Retry later |
| 500 | InternalError | Internal server error | Retry; if it keeps failing, provide X-Request-Id |
6. Notes โ
An async submission only means the task was accepted โ poll the query endpoint for the result. sync waits until the video is ready, usually 5โ20 s (see the table below for each scenario), and may take longer when queued; set the client timeout to 2 minutes or more
Resolution / duration Text only Text + first frame Text + reference image 768P / 5s ~5.2 s ~7.2 s ~7.5 s 768P / 10s ~8.7 s ~11.8 s ~10.6 s 768P / 15s ~13.8 s ~16.9 s ~15.3 s The number of concurrent generation tasks is limited; exceeding it returns 429 โ retry later
Poll every 2โ5 seconds and stop once
statusbecomessucceeded/failedA
failedtask is not retried automatically and must be resubmitted; seetask.errorin the query result (async) orMessagein the error envelope (sync) for the reasonOutput URLs are valid for 1 hour by default; when expired, call the query endpoint again to get a new URL โ the video is not regenerated
Billing is based on the submitted
duration, regardless of the actual output length; failed tasks are not billedTask records are kept for 7 days; after that, queries return 404 โ save outputs promptly
First/last-frame image URLs must be publicly accessible
Once a first frame is set, the video
ratiofollows the first frameReference image / video / audio, asset transfer,
callback_urland similar capabilities are not supported yet; passing them returnsInvalidParameter.UnsupportedFeature
7. Billing โ
Pricing โ
| Resolution | List price (CNY / second / day) |
|---|---|
| 480P | 0.3 |
| 768P | 0.5 |
| 1080P | 0.6 |
Billing rules โ
- Billing item: WAND-Vega-Video RTC video generation duration
- Billing rule: billed by generated video duration โ the cumulative generated duration in the billing cycle multiplied by the unit price of the corresponding resolution
- Formula: cost = generated video duration (s) ร unit price of the resolution
Billing example โ
If on October 20, 2026 you generate 10 videos of 5 seconds each at 768P, the bill payable on October 21, 2026 is:
5 (s/video) ร 10 (videos) ร 0.5 (CNY/s) = 25 CNY
Related Docs โ
| Doc | Description |
|---|---|
| WAND-Vega-Video (Tokenhub) | Call Vega-Video 1.0 / 1.5 Pro / Lite through Tokenhub, with reference image, video and audio support |