Skip to main content
POST
Estimate the price of an image-to-video animation request
Estimate the cost of a video animation (image-to-video) job before submitting it.

Authorizations

Authorization
string
header
required

Sanctum personal access token, sent as Authorization: Bearer <token>. The token is opaque — it carries no claims and no embedded expiry, so do not attempt to decode it. Issue and revoke tokens from your account dashboard.

Headers

Accept
enum<string>
default:application/json
required
Available options:
application/json

Body

application/json

Image to video price calculation parameters

Every example in this schema is a working set for the model example shown — they are not defaults and not portable. Sizes, step counts, frame counts and frame rates are all per-model: read info.limits and info.defaults for the model you actually intend to use from GET /api/v2/models. Substituting a different model while keeping these values is the most common source of a 422.

width
integer
required

Width of the generated video in pixels. The accepted range is model-specific — read info.limits.min_width/max_width and min_height/max_height for your model from GET /api/v2/models. Some models also publish dimension_multiple or resolution_step: values are snapped DOWN to that grid before validation, so an off-grid size is silently reduced rather than rejected. max_pixels and max_ratio, where present, cap total area and aspect ratio on top of the per-side bounds.

Example:

512

height
integer
required

Height of the generated video in pixels. The accepted range is model-specific — read info.limits.min_width/max_width and min_height/max_height for your model from GET /api/v2/models. Some models also publish dimension_multiple or resolution_step: values are snapped DOWN to that grid before validation, so an off-grid size is silently reduced rather than rejected. max_pixels and max_ratio, where present, cap total area and aspect ratio on top of the per-side bounds.

Example:

512

frames
integer
required

Number of video frames to generate. The accepted range is model-specific — read info.limits.min_frames/max_frames for your model from GET /api/v2/models; a value outside it is rejected with 422.

Example:

120

fps
integer
required

FPS of the generated video. The model dictates the value: read info.defaults.fps for your model from GET /api/v2/models. Where min_fps equals max_fps that is the only accepted value; anything outside the range is rejected with 422.

Example:

30

model
string
required

The model to use for video generation. Available models can be retrieved via the GET /api/v2/models endpoint.

Example:

"Ltxv_13B_0_9_8_Distilled_FP8"

steps
integer

Number of inference steps. Required when the model publishes step bounds: send it if info.limits.min_steps / max_steps or info.defaults.steps is present for your model in GET /api/v2/models, and stay inside that range. Key off those fields rather than info.features.supports_steps, which some models omit while still using steps.

Example:

1

Response

Calculated price for img2video inference.

data
object