veo/veo-3.1-lite-generate-001, served by Comfy Router from Veo.
Input: Text, Image, Video · Output: Video + Audio
Quick start
Create a key in your Comfy workspace and export it asCOMFY_API_KEY. The Python and TypeScript snippets use the Comfy SDKs (pip install comfy-sdk and npm install @comfyorg/sdk); the cURL snippet is the same call over raw HTTP.
Model ID: veo/veo-3.1-lite-generate-001
Endpoint: POST https://api.comfy.org/v2/models/veo/veo-3.1-lite-generate-001
- Wait for the result
- Queue and collect later
The same body, sent to
POST https://api.comfy.org/v2/models/veo/veo-3.1-lite-generate-001/requests. Router answers 201 with a request_id as soon as the run is admitted, and the result is collected once it is ready, from this process or another one. Queued delivery walks through status, cancellation and collection.Schema
Input
Camera motion type. Requires image to be provided.Possible values:
fixed, pan_left, pan_right, tilt_up, tilt_down, truck_left, truck_right, pedestal_up, pedestal_down, push_in, pull_outCloud Storage URI of the image. On a non-BYOK request a
gs:// URI (or its https://storage.googleapis.com form) naming a Comfy-owned bucket is refused with 400 unless the object is under your own POST /customers/storage prefix or is a video a previous Veo generate wrote for you.Optional last frame image. Used with image to generate video between first and last frames. Supported by Veo 3.0+ models.
Cloud Storage URI of the image. On a non-BYOK request a
gs:// URI (or its https://storage.googleapis.com form) naming a Comfy-owned bucket is refused with 400 unless the object is under your own POST /customers/storage prefix or is a video a previous Veo generate wrote for you.Cloud Storage URI to mask file. On a non-BYOK request a
gs:// URI (or its https://storage.googleapis.com form) naming a Comfy-owned bucket is refused with 400 unless the object is under your own POST /customers/storage prefix or is a video a previous Veo generate wrote for you.Optional reference images to guide video generation. Supports up to 3 asset images or 1 style image. Supported by Veo 3.1 models (preview).
Cloud Storage URI of the image. On a non-BYOK request a
gs:// URI (or its https://storage.googleapis.com form) naming a Comfy-owned bucket is refused with 400 unless the object is under your own POST /customers/storage prefix or is a video a previous Veo generate wrote for you.Optional input video for video extension or editing. Incompatible with image and referenceImages.
Cloud Storage URI of the input video. On a non-BYOK request a
gs:// URI (or its https://storage.googleapis.com form) naming a Comfy-owned bucket is refused with 400 unless the object is under your own POST /customers/storage prefix or is a video a previous Veo generate wrote for you.MIME type of the videoPossible values:
video/mov, video/mpeg, video/mp4, video/mpg, video/avi, video/wmv, video/mpegps, video/x-flvTarget duration of the generated video in seconds. Veo 2: 5-8. Veo 3/3.1: 4, 6, or 8. Default: 8
Whether to generate audio along with the video. Defaults to true. Supported by Veo 3.0+ models.
Controls people in generated videos. Default: allow_adult.
ALLOW and BLOCK are also accepted, for the same compatibility reason Veo2GenVidRequest’s personGeneration enum carries them (see the note at that component): ComfyUI’s Veo 3 partner node (comfy_api_nodes/nodes_veo2.py) always sends one of these two spellings, never Vertex’s own, to /proxy/veo/{model}/generate for veo-3.1-generate-001, veo-3.1-fast-generate-001 and veo-3.1-lite-generate-001 — the three ids this component is the Router input schema for. On a Router dispatch (model_provider=veo) for one of those ids, synchronous or queued (/v2/models/veo/{model}/requests), ALLOW is mapped to allow_adult and BLOCK to dont_allow before the request reaches Vertex (routerVeoMapPersonGeneration, server/middleware/router_veo_person_generation.go), because Vertex itself accepts neither spelling. A direct v1 /proxy/veo/:modelId/generate caller is unaffected either way: comfy-api installs no request validator on /proxy/*, so this enum was already unenforced documentation there, and the Router-only mapping does not run for it.Possible values: dont_allow, allow_adult, allowAll, ALLOW, BLOCKCloud Pub/Sub topic for progress updates (projects/{project}/topics/{topic}). Not accepted on Comfy-credentialed (non-BYOK) requests: the generate route answers 400 if it is present, because the operation runs in Comfy’s project and Vertex would publish as Comfy’s service agent. Accepted only on bring-your-own-key requests, where Vertex evaluates the topic grant in your own project.
Output video resolution. Supported by Veo 3.0+ models. Default: 720pPossible values:
720p, 1080p, 4kRandom seed for deterministic output. Different seeds used per video if sampleCount > 1.Format:
uint32Optional Cloud Storage destination for the generated videos, as a
gs:// URI.
IT MUST NAME A BUCKET OF YOUR OWN. Outside bring-your-own-key, this route runs under Comfy’s own Google Cloud credentials rather than yours, so a destination inside a Comfy-owned bucket would be a write performed by Comfy’s service account, into a shared layout, billed to Comfy’s project. A request naming one is refused with a 400 and nothing is generated — with one exception on a synchronous Comfy Router call (POST /v2/models/{provider}/{model}) where platform storage is enabled: a value naming Router’s own Veo or Gemini asset bucket is replaced with a destination Router mints under your own platform prefix for that call (see the Router Veo route), and only that exact Router-minted destination is let through. A queued Router submit (POST /v2/models/{provider}/{model}/requests) makes no such replacement, so it refuses that value with a 400 like any other Comfy-owned bucket. Any other destination is forwarded to Vertex unchanged and is yours to grant access to. A bring-your-own-key call runs in your own project and is forwarded as sent.Operation type for the video generation requestPossible values:
textToVideo, imageToVideo, referenceToVideo, edit, extend, upscaleGET /v2/models/veo/veo-3.1-lite-generate-001/openapi.json, the same document it validates a call against before the request reaches the provider.
Output
Examples
Input
Output
Before you ship
The SDKs create anIdempotency-Key and reuse it for automatic retries. For manual retries, reuse the original key. Router can hold the connection for up to 10 minutes.
When a request fails, Router sends an X-Comfy-Error-Type response header explaining why. A 422 means Router rejected the input before calling the provider, and a 413 means the request body was larger than Router accepts. Download generated assets promptly because result URLs can expire.
Any size limit named in a field description above is the provider’s own bound on that field, quoted from the provider’s specification. Router applies a separate cap to the whole request body, which base64-encoded media counts against: see request body size.
This page documents one partner model called through Comfy Router. The same comfy-sdk / @comfyorg/sdk package also ships a second client, for running a whole ComfyUI workflow graph on Comfy Cloud: Comfy(api_key=...) / new Comfy({ apiKey }), with client.workflows, client.assets and client.jobs. See Comfy SDKs.
Headers
Authentication, idempotency, request IDs, error buckets, retry pacing, spend limits.
Using the Router API
Model discovery, validation errors, retries, and billing.
Limitations
What Router does not do today, and what to use instead.