Skip to main content
Use ltx/ltx-2-5-fast with the Comfy Router API. LTX 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: ltx/ltx-2-5-fast Endpoint: POST https://api.comfy.org/v2/models/ltx/ltx-2-5-fast

Schema

Input

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

Output

string
Job completion timestamp (ISO 8601)
string
Job creation timestamp (ISO 8601)
object
Present when status is failed
string
string
string
Unique job identifier
object
Present when status is completed; output URLs expire 24 hours after completion
string
URL of the generated video
string
Job status (pending, processing, completed, failed)

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.