One exact five-second SDR scope
Luma Ray 3.2 API pricing
See the result first for Ray 3.2 text-to-video at 720p, five seconds, SDR, no references, no loop, and no HDR or EXR export.
Luma Ray 3.2 API pricing
Ray 3.2 720p SDR five-second price
- Reviewed comparison scope
- Luma Ray 3.2 · text to video · SDR · 720p · 5 seconds · no references or loop · global · USD per request
- Publication gate
- At least 3 unique providers with accepted, fresh, reviewed evidence
| Price rank | Provider | Route and tier | Published meter | Evidence |
|---|---|---|---|---|
| 1Tie | Luma API | official · standard SDR | $0.3 / source requestfresh | First-party sourceChecked Aug 23, 2026Fresh until Aug 30, 2026 |
| 1Tie | Replicate | marketplace · standard SDR | $0.3 / source requestfresh | First-party sourceChecked Aug 23, 2026Fresh until Aug 30, 2026 |
| 3 | fal.ai | aggregator · standard SDR | $1 / source requestfresh | First-party sourceChecked Aug 23, 2026Fresh until Aug 30, 2026 |
Price meter only: HDR, EXR export, start or end frames, image-to-video, looping, ten-second output, reframe, and video-to-video use different constraints or prices and are excluded. Equal prices share a price rank; provider name and offer ID determine only their stable display order.
Configuration-specific buying guide
How to use this Luma Ray 3.2 API pricing result
Ray 3.2 exposes enough controls that a family-level price is almost useless. This result fixes text-to-video, standard dynamic range, 720p, a five-second duration, no reference frames, no loop, and one output. Luma and Replicate publish thirty cents for that request. fal publishes one dollar for the same reviewed settings. The three-channel gate therefore permits a price order for this configuration only.
The exact release matters. Older Ray 2 documentation remains online, while Luma announced Ray 3.2 in June 2026 and now documents it through the Agents API. Ray 3.14 also appears in Luma's current product material, but it is a different model and cannot inherit Ray 3.2 prices. APIDir keeps the canonical ray-3.2 identity attached to every row.
A large spread can be real without proving that the services are interchangeable. Provider throughput, queuing, support, regional availability, request fields, output hosting, and account limits may differ. The result ranks a documented five-second request, not cinematic quality, latency, uptime, or enterprise value.
What changes the real cost
- Resolution changes the fixed request price sharply; 540p, 720p, and 1080p must remain separate.
- Five- and ten-second SDR requests use different totals rather than a single universal per-second multiplier.
- HDR and EXR export introduce separate eligibility rules and prices, and HDR is not a label that can be ignored.
- Reference frames, looping, reframe, video-to-video, storage, retries, and failed-work policies affect the real budget.
Checks before production
- Pin ray-3.2 and verify that a provider route has not silently moved to Ray 3.14 or a legacy Ray model.
- Send resolution, duration, HDR, EXR, loop, and reference settings explicitly rather than accepting dashboard defaults.
- Stop polling on every documented terminal state and cap both elapsed time and retry count.
- Store the resolved model, settings, output count, request ID, charge, and source check date with each job.
Workloads this result can inform
Fast storyboard drafts
Use the exact five-second SDR scope as a repeatable baseline, then compare queue time and usable-output rate before choosing only by the request price.
HDR production shots
Leave this ranking and use the provider's HDR table. A standard 720p result cannot be stretched into an HDR or EXR estimate.
Reference-guided motion
Start and end frames change supported duration and loop behavior. Validate that configuration independently even if the provider advertises one Ray 3.2 family page.
Public methodology
How an offer enters the ranking
- The observation passed APIDir's accepted evidence and publication-permission gates and retains an official first-party source.
- Its offer identity, provider channel, route, and tier are explicitly included after configuration review.
- Its freshness label is fresh and its fresh-until time has not passed.
- The model, billing unit, region, and every reviewed comparison field match the group definition.
- At least three unique providers qualify; otherwise APIDir publishes no order, cheapest claim, or spread.
- Prices sort low to high. Equal prices share a rank; provider name, then offer ID, controls only stable display order.
Questions developers ask
When does APIDir publish a cheapest provider?
Only when at least three unique providers have accepted, publication-permitted, fresh observations for the same model and billing meter, with every route and material configuration field explicitly reviewed.
What happens to stale or quarantined prices?
They are excluded from ranking order. Historical evidence may remain auditable elsewhere, but it cannot support a current winner or savings claim.
Does the first row mean the provider is best overall?
No. The order covers the displayed price meter only and does not score quality, speed, uptime, limits, support, legal terms, or total production cost.
APIDir Delta · controlled rollout
Join the source-linked pricing update waitlist.
Confirm your address to join the waitlist. Editorial delivery starts only after sender, suppression, and evidence checks are active.