Wan 3.0 Video Prime

Generate a video from a text prompt using Alibaba Wan 3.0 Video Prime, the fast variant, at 720P with audio, or animate a still image you supply as the first frame. Clips run 2 to 30 seconds and render in a fraction of the standard model’s time. Returns the URL of the generated MP4. That URL is temporary: Goro holds a run’s results for 24 hours and nothing guarantees the file outlives that, so collect what you need within 24 hours.

Use when turnaround matters more than the last cent: iterating on a shot, generating several candidates in one session, or feeding a pipeline that waits on the result. Same capabilities as Wan 3.0 video, faster end to end, at a higher rate per second. To animate a local or private image, upload it first (POST /v1/uploads, or create_upload over MCP, or goro run —image) and pass the handle as image_handle. Billed per second of video you ask for.

Price

$0.2520 per second of video. An exact rate, not an estimate. The total is that rate times the seconds of video in your request, so you can work out what a call costs before you make it. No call costs less than

0.0020 or more than

7.56, the price of the largest request this endpoint takes, 30 seconds of video. discover and inspect quote your exact request before it runs.

Input

Field	Type	Required	Notes
`audio`	`boolean`		Whether the output carries an audio track. Does not change the price. Defaults to `true`.
`prompt`	`string`	yes	What to film. Describe the subject, the action, the camera move, the lighting and the mood. Chinese and English both work.
`duration`	`integer`		Length of the generated video in seconds. This is what you are billed on, and it is the only field that changes the price. Defaults to `5`.
`image_urls`	`array`		Optional. One public http or https link to the image the video should start from (JPEG, PNG or WEBP, up to 10 MB). Use this when the image is ALREADY published somewhere; the output URL of an image endpoint works directly. Nothing is copied or re-hosted, we pass the link on. For a file that is not already public, use image_handle instead and it never has to be published anywhere. Send one of the three, never two.
`resolution`	`720P`		Fixed at 720P (the model spells its resolutions with a capital P). Resolution changes the price per second, and this endpoint quotes one exact rate, so 480P and 1080P would get their own endpoints. Defaults to `"720P"`.
`aspect_ratio`	`adaptive`, `16:9`, `4:3`, `1:1`, `3:4`, `9:16`		Shape of the output video. adaptive follows the starting image when there is one. Defaults to `"16:9"`.
`image_base64`	`string`		Optional, and only for a SMALL image (under 3 MB) or a caller that cannot run a shell command. The image inline, as base64 of the file’s own bytes; a data:image/png;base64, prefix is accepted and its declared type ignored. Understand the cost before choosing it: this string is part of the request, and on an MCP call the request IS the tool arguments, which pass through the model’s context window. A 3 MB photograph is 4 MB of base64, on the order of a million tokens, and in practice it is truncated and the run fails looking like file corruption. Do not downscale an image to fit here: use image_handle, which takes up to 10 MB and keeps the file out of the conversation entirely. The 3 MB ceiling is 4,194,304 base64 characters and is a property of the request body, not of the model. JPEG, PNG or WEBP, checked against the file’s own leading bytes rather than against any type you declare. Send one of the three, never two.
`image_handle`	`string`		Optional, and the RIGHT WAY to send a local or private image. Upload the file first with POST /v1/uploads (or the create_upload MCP tool, or the CLI’s —image flag, which does the whole thing for you) and put the short handle it returns here. The file goes straight from you to a private bucket: it never passes through a tool call, so it never passes through a model’s context window, and up to 10 MB is fine. Nothing is published. The handle is usable for 10 minutes after the upload lands and the file is deleted 30 minutes after that. Supplying it makes this an image-to-video call, at exactly the same price. Send one of image_handle, image_urls and image_base64, never two.

These are all the fields this endpoint accepts. Anything else is rejected as a validation_error rather than forwarded to the provider.

Example

curl -X POST https://api.usegoro.ai/v1/run \
  -H "Authorization: Bearer $GORO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"slug":"video.wan_prime","input":{"prompt":"A cyclist crossing a rain-slick city street at night, neon reflections, tracking shot."}}'

Response

The full response. Values are illustrative.

[
  "https://example.com/goro/generated-video-1.mp4"
]

Guide

CLI reference

API reference

Tools

Wan 3.0 Video Prime

Price

Input

Example

Response

​Price

​Input

​Example

​Response

Price

Input

Example

Response