Skip to main content
API Reference for veo/veo-2.0-generate-001, served by Comfy Router from Veo.

Quick start

Create a key in your Comfy workspace and export it as COMFY_API_KEY. The Python and TypeScript snippets use the Comfy SDKs (pip install comfy-sdk, npm install @comfyorg/sdk); the cURL snippet is the same call over raw HTTP. Model ID: veo/veo-2.0-generate-001 Endpoint: POST https://api.comfy.org/v2/models/veo/veo-2.0-generate-001

Schema

Input

object[]
object
Optional image to guide video generation
string (byte)
Format: byte
string
string
string
required
Text description of the video
object
string
integer
boolean
string
string
Controls people in generated videos. dont_allow, allow_adult and allowAll are Vertex AI’s own spellings and are the ones VeoGenVidRequest publishes for the same field. ALLOW and BLOCK are kept for compatibility with clients generated from this component before it was Router-authored — see the note at the top of Veo2GenVidRequest.Possible values: ALLOW, BLOCK, dont_allow, allow_adult, allowAll
integer
integer
Format: uint32
string
Optional Cloud Storage URI to upload the video
Generated from the schema Router serves at GET /v2/models/veo/veo-2.0-generate-001/openapi.json, the same document it validates a call against before the request reaches the provider.

Output

boolean
Whether the operation has completed
object
Error details, present if the operation failed
integer
gRPC error code
string
Error message
string
Operation resource name
object
The prediction response, present when done is true
string
integer
Number of videos filtered by responsible AI policies
string[]
Reasons why videos were filtered by responsible AI policies
object[]
string
Base64-encoded video content
string
Cloud Storage URI of the generated video
string
Video MIME type (video/mp4)

Examples

Input

Output

Before you ship

The SDKs create an Idempotency-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. Download generated assets promptly because result URLs can expire.

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.