bria/video-edit-green-screen, served by Comfy Router from Bria.
Quick start
Create a key at platform.comfy.org/profile/api-keys 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
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
Router does not publish an output schema for this model.Examples
Input
Before you ship
The snippets above are the shortest working call. Three things are the same for every model and are documented once on the Comfy Router headers page: send anIdempotency-Key on every paid call and reuse it when you retry, expect the connection to be held up to Router’s 10 minute deadline, and keep X-Comfy-Request-Id from every response. The SDKs do all three for you; the cURL tab does none of them. On failure, X-Comfy-Error-Type names the bucket, and a 422 means the body failed the model’s schema and was never billed.
Headers
Authentication, idempotency, request IDs, error buckets, retry pacing, spend limits.
Quick Start
Typed error handling in Python and TypeScript, reading the 422, walking the catalog.
Limitations
What Router does not do today, and what to use instead.