Skip to main content
Use veo/veo-2.0-generate-001 with the Comfy Router API. Veo provides the model; Router gives it the shared authentication and request route below.

Quick start

Create a key at platform.comfy.org/profile/api-keys 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

Router has not published an authored input schema for this model yet: GET /v2/models/veo/veo-2.0-generate-001/openapi.json returns an open object with x-comfy-input-schema-authored: false. Router forwards the body to Veo unchanged, so Veo’s own API reference is authoritative for the request fields, and nothing is validated server side.

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

Output

Before you ship

Save one Idempotency-Key for each call and reuse it for retries. Router can hold the connection for up to 10 minutes. The SDKs handle authentication; raw HTTP clients send the headers themselves. Use X-Comfy-Error-Type to classify a failure. 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

Find models, inspect schemas, and retry safely.

Limitations

What Router does not do today, and what to use instead.