bria/video-edit-green-screen, served by Comfy Router from Bria.
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, npm install @comfyorg/sdk); the cURL snippet is the same call over raw HTTP.
Model ID: bria/video-edit-green-screen
Endpoint: POST https://api.comfy.org/v2/models/bria/video-edit-green-screen
- Wait for the result
- Queue and collect later
Schema
Input
string
The solid background shade applied behind the foreground for chroma keying. Defaults to broadcast_green.Possible values:
broadcast_green, chroma_green, blue_screenstring
Output container and codec preset.Possible values:
mp4_h264, mp4_h265, webm_vp9, mov_h265, mov_proresks, mkv_h264, mkv_h265, mkv_vp9, gifboolean
Whether to preserve audio from the input video.
string
required
Publicly accessible URL of the input video. Input resolution supported up to 16000x16000 (16K). Max duration 60 seconds.
GET /v2/models/bria/video-edit-green-screen/openapi.json, the same document it validates a call against before the request reaches the provider.
Output
object
Error object (only present when status is ERROR)
integer
Error code.
string
Additional error details.
string
Error message.
string
Unique identifier for the request.
object
Result object (only present when status is COMPLETED)
string
URL of the generated/edited image.
string
Original prompt.
string
Refined version of the prompt, or null on a COMPLETED generation Bria did not refine. Nullable because the key is PRESENT carrying null rather than omitted; observed live on bria/image-edit-gen-fill.
integer
Seed used for generation.
string
The detailed JSON structured prompt.
string
URL of the generated video.
string
Current status of the request.Possible values:
IN_PROGRESS, COMPLETED, ERROR, UNKNOWNExamples
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. 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.