ltx/ltx-2-5-fast, served by Comfy Router from LTX.
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: 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
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.