fal/crystal-video-upscaler, served by Comfy Router from fal.
Input: Video · Output: Video
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: fal/crystal-video-upscaler
Endpoint: POST https://api.comfy.org/v2/models/fal/crystal-video-upscaler
- Wait for the result
- Queue and collect later
The same body, sent to
POST https://api.comfy.org/v2/models/fal/crystal-video-upscaler/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
number
default:"2"
Factor applied to each side of the input video. The upscaled video must not exceed 5K. fal bills per output megapixel per second, so the price grows with the square of this value.Range:
1 to 200string
required
URL of the input video (MP4, MOV, WebM, M4V or GIF).
GET /v2/models/fal/crystal-video-upscaler/openapi.json, the same document it validates a call against before the request reaches the provider.
Output
object
required
The upscaled video file.
string
MIME type of the video file.
number
Duration of the video in seconds.
string
Name of the video file.
integer
Size of the video file in bytes.
number
Frame rate of the video.
integer
Height of the video in pixels.
integer
Number of frames in the video.
string
required
URL of the upscaled video.
integer
Width of the video in pixels.
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.