Luma AI · video · exact comparison
Luma Ray 3.2 API providers and route evidence
Compare Luma Ray 3.2 API routes at the same SDR, resolution, duration, mode, region, and fixed-request billing scope.
Model-level provider comparison
Luma Ray 3.2 price ranking status
Current answer: APIDir currently publishes 1 comparable price ranking. Keep each meter and configuration separate before choosing a route.
- Provider routes with evidence
- 3
- Accepted observations
- 3
- Billing meters
- source request
- Latest accepted check
- Aug 23, 2026
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.
Uncollapsed source records
All accepted offer evidence
These rows remain separate until their offered model ID, route, meter, tier, resolution, duration, audio, and region are proven comparable.
| Provider | Model | Configuration | Recorded price | Evidence |
|---|---|---|---|---|
| Luma APIofficial | Luma Ray 3.2 | model: ray-3.2 · text-to-video · standard SDR · 720p · 5s · no audio · source unit: $0.30 per five-second 720p SDR T2V/I2V video | $0.3 / source requestfresh | Provider sourceChecked Aug 23, 2026 |
| Replicatemarketplace | Luma Ray 3.2 | model: luma/ray-3.2 · text-to-video · standard SDR · 720p · 5s · no audio · source unit: $0.30 per five-second 720p SDR output video | $0.3 / source requestfresh | Provider sourceChecked Aug 23, 2026 |
| fal.aiaggregator | Luma Ray 3.2 | model: luma/agent/ray/v3.2/text-to-video · text-to-video · standard SDR · 720p · 5s · no audio · source unit: $1.00 per five-second 720p SDR video | $1 / source requestfresh | Provider sourceChecked Aug 23, 2026 |
Checked evidence, not a ranking: fresh rows were checked against the linked first-party source on the shown date. APIDir does not name a cheapest provider unless exact configurations and units match. Recheck before purchasing.
Developer resources
Provider documentation and pricing links
Compare integration documentation beside the exact first-party source used for each accepted observation.
| Provider | Channel | Developer resources | Accepted evidence |
|---|---|---|---|
| fal.ai | aggregator | DocumentationPricing page | 1 observationEvidence source 1 |
| Luma API | official | DocumentationPricing page | 1 observationEvidence source 1 |
| Replicate | marketplace | DocumentationPricing page | 1 observationEvidence source 1 |
Decision guide
How to compare Luma Ray 3.2 API providers
Luma Ray 3.2 is the June 2026 Ray release exposed through Luma's current Agents API and hosted provider routes. It should not be collapsed into legacy Ray 2 documentation, the broader Ray 3 family, or the newer Ray 3.14 product. APIDir records ray-3.2, luma/ray-3.2, and luma/agent/ray/v3.2/text-to-video as reviewed route identities for the same exact release.
The comparable price scope is deliberately small: text-to-video, standard dynamic range, 720p, five seconds, no start or end frame, no loop, no HDR, no EXR export, and one output. Luma and Replicate publish thirty cents for this request, while fal publishes one dollar. Three matching channels permit a narrow price order without implying equivalent service quality.
Ray 3.2 has materially different prices and constraints for 540p, 1080p, ten-second output, HDR, EXR, video-to-video, reframe, and reference-guided generation. A production choice must also consider queue time, throughput, regional availability, asset retention, support, and whether every required control is exposed through the hosted route.
What changes Luma Ray 3.2 API cost
- Five- or ten-second duration and the selected 540p, 720p, or 1080p output tier
- SDR versus HDR and whether an EXR file is requested for downstream grading
- Text, start-frame, end-frame, loop, reframe, or video-to-video workflow boundaries
- Retries, failed generations, output storage, delivery bandwidth, compositing, and review
Integration checks before production
- Pin Ray 3.2's exact route and block silent substitution with Ray 2, Ray 3, or Ray 3.14
- Make duration, resolution, HDR, EXR, loop, and reference inputs explicit in the request
- Reject invalid combinations before submission and stop polling on every documented terminal state
- Capture route, configuration, request ID, output count, terminal error, latency, and final charge
Workloads this comparison can inform
Storyboard and previsualization
Use a repeatable five-second SDR baseline to compare provider latency and usable-output rate without paying for higher delivery formats during early iteration.
Professional HDR finishing
Review the HDR and EXR table separately and test the target color pipeline. The standard 720p row is not an HDR budget.
Reference-controlled shots
Check start and end frame rules, duration restrictions, and loop compatibility on the exact provider endpoint before automating a sequence.
How to read the price result
Three channels pass the five-second 720p SDR scope. The price order applies only to that request and does not rank cinematic quality, speed, uptime, limits, or support.
Related model price comparisons
Use this evidence safely
A recorded price is not a complete production quote. Open the source, reproduce the exact configuration, and include retries, failed work, storage, egress, support, rate limits, and downstream processing in total cost.
Questions developers ask
What makes two Ray offers comparable?
The model version, generation mode, tier, resolution, duration, audio setting, region, and billing unit must match.
Does APIDir name a cheapest provider on this page?
Only when at least three explicitly reviewed provider offers are fresh, publication-permitted, and within the same published comparison scope. Stale or mismatched evidence cannot support that claim.
How should I confirm a budget?
Open the linked provider source, verify the configuration, then calculate your own successful and failed workload volume.
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.