Use Flashvsr with Comfy Router

Call wavespeed/flashvsr through Comfy Router: endpoint, request shape and the response Router returns.

API Reference for wavespeed/flashvsr, served by Comfy Router from WaveSpeed.

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: wavespeed/flashvsr

Endpoint: POST https://api.comfy.org/v2/models/wavespeed/flashvsr

Python

from comfy_sdk import Comfy

# Reads COMFY_API_KEY from the environment.
# The SDK automatically creates an idempotency key and reuses it for automatic retries.
with Comfy() as client:
    result = client.models.run(
        "wavespeed/flashvsr",
        {
            "duration": 4,
            "target_resolution": "1080p",
            "video": "https://samplelib.com/mp4/sample-30s.mp4",
        },
    )

print(result)

Schema

Input

duration · number · required

Duration of the video in seconds

target_resolution · string · default: "\"1080p\""

Target resolution to upscale to.

Possible values: 720p, 1080p, 2k, 4k

video · string · required

The video to upscale. Can be a URL to the video file or a base64-encoded video.

Generated from the schema Router serves at GET /v2/models/wavespeed/flashvsr/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

{
  "duration": 4,
  "target_resolution": "1080p",
  "video": "https://samplelib.com/mp4/sample-30s.mp4"
}

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.