pika/pika-2.5-text-to-video, served by Comfy Router from Pika.
Input: Text · 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: pika/pika-2.5-text-to-video
Endpoint: POST https://api.comfy.org/v2/models/pika/pika-2.5-text-to-video
- Wait for the result
- Queue and collect later
The same body, sent to
POST https://api.comfy.org/v2/models/pika/pika-2.5-text-to-video/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
Video length in seconds. Text-to-video produces five-second clips only.Possible values:
5GET /v2/models/pika/pika-2.5-text-to-video/openapi.json, the same document it validates a call against before the request reaches the provider.
Output
Pika’s structured failure record, set on a
failed job. Router answers a failed job with its own error response, so a body Router returns does not carry it; it is declared because it is part of Pika’s job document.Possible values:
invalid_input, content_moderation, provider_error, provider_timeout, provider_unavailable, rate_limited, insufficient_balance, membership_required, cycle_limit_exceeded, admission_suspended, usage_limit_exceeded, timed_out, internalThe finished job’s media, set when
status is completed. media_type says which field carries it: image fills images, video fills video, and videos fills videos.Lifecycle state. A body Router returns always reads
completed; a failed job is answered with Router’s error response instead.Possible values: queued, running, completed, failedProvider-reported units for the job. Keys are sparse; only the units the job reports are present.
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.