Skip to main content

LTX 2.3 Spicy LoRA is an uncensored image-to-video build on Lightricks' LTX 2.3 with thirteen built-in LoRAs. Pick the tuned or original preset and re-weight up to three LoRAs from 0 to 4; clips run 3 to 20 seconds at 480p to 1080p.

From $0.029/s5% below the Spicy list price

Workbench

Input

Image to video
Optional. Describe the beat, the camera and the pacing; do not re-describe the frame.
Style preset
TunedOriginal
The default, tuned, applies the recommended built-in LoRA set; original styles more lightly and stays closer to the source frame - pick it when tuned fights the look you wrote.
1/1

Drop files or media links, paste, or browse · 1 file · Max 10 MB · JPG · PNG · WEBP · GIF

  • 1
1 / 1 files
Required. The still that animates - it decides the content and the output shape.
Style LoRAs1/3
Item 1
Key of a built-in LoRA.
Strength
Strength for this LoRA, 0 to 4; 0 turns it off. Defaults to 1. no lower than 0 · no higher than 4
Up to three {path, scale} entries: path is one of the thirteen built-in LoRA keys, scale its strength from 0 to 4 (default 1). Applied on top of the preset. at most 3 items
Durationaffects price
Whole seconds, 3 to 20. Sweep LoRA strengths at 3 before generating 20. no lower than 3 · no higher than 20
affects price
480p, 720p or 1080p. It defaults to 480p - raise it for anything you deliver.
Seed
Hold it constant across a strength sweep so the LoRA strength is the only variable. no lower than 0 · no higher than 2147483647
Safety checkerOff

SpicyAPI does not run a safety checker on this model. Your prompt and media go to the model as written, and the model itself decides what comes back.

Checking your account before enabling submission and pricing.

Output

Ready for a new run
Example result

Related models and next tasks

Missing the model you need?

Tell us what to add and where you would use it. Requests go to the people who decide what gets onboarded next.

These previews show selected examples. Try your own prompt and settings in the Playground.

Retune built-in LoRAs instead of hosting weight files

LTX 2.3 Spicy LoRA is an uncensored image-to-video endpoint: it takes one opening frame, an optional prompt, and returns a clip of 3 to 20 seconds at 480p, 720p or 1080p. What it adds over the base LTX 2.3 Spicy family is a single field, loras, which names up to three of the model's thirteen built-in LoRAs by key and sets each one's strength from 0 to 4 on top of the chosen preset.

Open the playground
Retune built-in LoRAs instead of hosting weight files
Required input
image_url only; prompt, preset and loras are all optional
Output
3–20 whole seconds at 480p, 720p or 1080p (480p is the default)
Preset
tuned (default) or original; every loras entry applies on top of either
Per-LoRA overrides
Up to 3 entries, each a built-in key with strength 0–4 (default 1)
Built-in LoRA library
13 fixed keys in the loras enum; no custom weight file or URL is accepted
Billing
Per second of output; duration_seconds and resolution are the only pricing dimensions
Mechanism
Name a built-in LoRA, don't host a fileloras.path takes one of thirteen keys from a fixed enum, so a look travels as a few keys and numbers rather than a weight file somebody has to keep online. Wan 2.2 Spicy LoRA works the other way round: there, loras.path is a URL pointing at weights you host yourself.
Pricing
LoRA settings don't move the quoteBilling runs per second of output, and duration_seconds and resolution are the only two pricing dimensions. A request carrying three loras entries quotes the same as a bare one at the same length and resolution tier.
Base contract
Everything LTX 2.3 Spicy has, plus one fieldThe two families publish the same schema apart from loras: a required image_url, an optional prompt, duration_seconds from 3 to 20, three resolution tiers, seed and the same tuned/original preset. Porting a working request means adding one field and the new model name, not rewriting the body.

What LTX 2.3 Spicy LoRA does

The preset field sets the starting stack

The preset field sets the starting stack

preset is a two-value enum. tuned is the default and loads the recommended built-in mix; original leaves the frame more lightly styled. Choose between them first, because every loras entry is applied on top of whichever one you send, and the base family offers the same two values on the same field.

Per-LoRA strength overrides

Per-LoRA strength overrides

loras is a per-request array, so two calls a minute apart can carry different strengths with nothing to save or reset in between. Each of the three slots holds one {path, scale} object: path is a key from the schema enum and the only part of the object the endpoint requires, while scale accepts fractions as well as whole numbers, so 0.6 and 3.5 are both valid.

  • The same duration range as the base family

    duration_seconds is still any whole number from 3 to 20, with 5 as the default. Adding overrides doesn't narrow that range or push you onto fixed lengths, so a shot that has to land at 13 seconds still lands at 13 seconds with three loras entries in the request.

  • The same three resolution tiers as the base family

    480p, 720p and 1080p are all available here, and resolution defaults to 480p, so raise it deliberately for anything you deliver. The tier is independent of the LoRA fields: a preset and a set of strengths you settled at 480p can be sent again at 1080p with the LoRA entries untouched.

  • No extra cost for LoRA settings

    The pricing dimensions on this endpoint are duration_seconds and resolution. An empty loras array and one holding three entries at strength 4 quote the same amount at the same length and tier, so a strength comparison costs whatever those clips would have cost anyway.

  • A fixed seed makes a strength sweep readable

    seed accepts any integer from 0 to 2,147,483,647. Hold it steady along with the frame, prompt, duration and resolution while you move one loras entry, and that strength is the only thing you changed between the two clips. Identical output is still not guaranteed, so read each render as a fresh take.

Who reaches for LTX 2.3 Spicy LoRA

  • No weight file to host or maintain

    Giving a recurring character a fixed look

    No weight file to host or maintain

    A treatment that already lives inside the preset needs no storage, no upload step and no link for anyone to keep alive. The whole look is one preset value plus a few key-and-strength pairs, short enough to sit in a config file and be versioned with the rest of the project.

  • The same overrides across every beat

    A roleplay series with one recurring character

    The same overrides across every beat

    Settle the preset and the loras entries once, then send the same pair with every frame in the series. The styling that holds a companion character's scenes together comes from identical keys and strengths each time, instead of being argued again in prose for every new shot.

  • Comparison costs what the clips cost

    Tuning strengths on a small budget

    Comparison costs what the clips cost

    preset and loras sit outside the pricing dimensions, so a sweep of tuned against original, or of one key at half strength against the same key at double, bills exactly like the same clips with no overrides. Sweep at the short end of the duration range before committing to a long render.

  • This isn't that endpoint

    Teams that already have their own weights

    This isn't that endpoint

    A project that depends on a specific weight file somebody trained has nowhere to put it here, because loras only names LoRAs already inside the model. Wan 2.2 Spicy LoRA is the bring-your-own-weights endpoint in this catalog, and it reads loras.path as a URL instead of a key.

How to call the LTX 2.3 Spicy LoRA API

  1. Run the default preset with no overrides first

    Send image_url, an optional prompt and a duration on tuned with loras left out entirely. That clip is the baseline every override gets judged against, and if tuned pulls against the look you wrote, compare it with original before touching any individual key.

  2. Override one key at a time

    Add a single loras entry at scale 1 and change nothing else in the request. A run that moves three keys at once tells you very little about any one of them, so learn what one key does to your frame before spending a second slot.

  3. Move the strength before adding a second entry

    Re-send the same request with that entry at a lower and then a higher scale to see what the key contributes at each point, holding the frame, prompt and seed fixed. Settle on one number before adding a second entry; the third slot is rarely needed.

  4. Pin the seed once a combination reads right

    Fix seed, keep preset and the loras entries as they are, and change duration or resolution on their own. Those parameters move independently of each other, so stepping up a tier doesn't mean tuning the strengths again from scratch.

LTX 2.3 Spicy LoRA worked examples

  • A single override at scale 0.6

    preset left at tuned and one loras entry at scale 0.6, 8 seconds at 720p. Enough to see what that key contributes without letting it run the shot.

    The character leans against the doorway, arms crossed, a slow half-turn toward camera; even overcast light, static medium shot
  • Two strengths in one clip

    Two loras entries on top of tuned: one key at scale 0.2, a second at 0.5, both applied to the same render. The rest of the preset stack runs unchanged.

    The character walks slowly toward camera down a dim hallway, single light source ahead, unhurried pace
  • A baseline with no overrides

    The same frame and prompt with loras left empty, so tuned runs as shipped. Render this first as the reference every override is compared against, then once more on original to see the lighter end of the range.

    The character tilts their head toward the window, hair shifting as they breathe in; soft side light, slow handheld drift

LTX 2.3 Spicy LoRA API questions

Start on tuned with loras left out, then change one key at a time and write down what worked: a preset value plus up to three {path, scale} entries is the entire description of a look on this endpoint, short enough to paste into a ticket. Keep seed fixed while you sweep a strength, and raise resolution only once the combination reads right. When the direction needs a weight file you trained yourself, Wan 2.2 Spicy LoRA is the endpoint that accepts one.