Video Models

Luma AI

Ray 1.5

Retained app label with an unresolved ray2 mapping. Read the routing notice before assuming a distinct Ray 1.5 endpoint.

Mapping unresolvedVideo

At a glance

Plan the shot before you generate.

App mapping & provider reference
Workflow / inputs
App video choice; exact endpoint input schema unresolved
Resolution reference
Not verified for this named route
Duration reference
App card label: 5 seconds
Audio reference
Not verified for this named route
Serving host
Luma (exact model mapping unresolved)
Catalog status
App-listed in owner audit; not live-tested

API model or route: Audit config: lumaModel = ray2; final request unresolved

App catalog ID: ray-1-5

Capabilities & boundaries

What it supports. What the app exposes.

Provider features and app integration are different layers. A feature in the upstream documentation is not automatically enabled in your workspace.

Model and hosting capabilities

  • Ray 1.5 appears as a separate app card in the supplied audit.
  • Its recorded configuration points to ray2, requiring inspection of the final Luma request before asserting the served model.
  • Simple comparison briefs can help validate identity and output behavior once the route is confirmed.

Before you choose

  • The current Luma documentation names Ray 2 and Ray Flash 2; it does not resolve this app card's older label.
  • A configuration conflict is not a provider retirement announcement. No shutdown date or historical price is inferred.
  • Review motion, anatomy, continuity and any generated sound before publishing. Prompt instructions are creative targets, not guarantees of an exact result.
  • Only upload media you have permission to use, including consent for identifiable performers. Provider safety rules and usage terms still apply.

Controls in the audited app integration

  • The card advertises a 5-second maximum, but the final handler body was not verified.
  • Do not assume the Ray 2 keyframe, resolution, extension or audio controls apply to a genuine Ray 1.5 route.

Put it to work

Start with a more useful visual brief.

Original examples from EZ Ai Assist. Choose supported controls separately. Some workflows require source media; a text brief does not supply those inputs.

Workflow 01

Route comparison baseline

Start with one clear action and a restrained camera move. Select supported duration and framing separately, then inspect continuity in the result.

A plain white cube rests on a blue tabletop as a soft shadow moves slowly across it. Use a fixed camera and preserve all straight edges and proportions. Add no other objects or text; keep the simple composition consistent so output differences are easy to review.

Workflow 02

Motion baseline

Start with one clear action and a restrained camera move. Select supported duration and framing separately, then inspect continuity in the result.

A single maple leaf floats gently across calm water from left to right. Keep the camera directly overhead and maintain the same lighting throughout. Preserve the leaf's outline and natural ripples, with no extra leaves, sudden acceleration or scene transitions.

Workflow 03

Texture baseline

Start with one clear action and a restrained camera move. Select supported duration and framing separately, then inspect continuity in the result.

A wool scarf hangs over the back of a simple wooden chair and moves slightly in a breeze. Use a locked medium shot and soft daylight. Keep the chair geometry and woven texture stable, with an empty background and no additional props or lettering.

Developer reference

Provider & hosting API pricing

Public provider or hosting API reference prices in USD, not EZ Ai Assist subscription prices or app charges. Check the app for your current plan, allowance and charge before generating.

View EZ Ai Assist plans

Pricing is unresolved until the final model mapping is confirmed. Ray 1.6, Ray 2 and Ray Flash 2 prices must not be relabeled as Ray 1.5 prices.

  • Provider prices can change. Verify the exact hosting route and request settings before relying on a published rate.
  • The owner audit found differences between some app-card estimates and backend calculations. This website update does not change or certify app billing.

Common questions

Ray 1.5 FAQs

What is Ray 1.5 useful for?

Ray 1.5 is retained with an explicit app-mapping conflict: the audited configuration points to ray2. No Ray 2 specifications are silently assigned to this name.

Which inputs does this workflow need?

App video choice; exact endpoint input schema unresolved. Confirm that the app accepts any required media before using a provider-only workflow.

What duration and resolution can I use?

App card label: 5 seconds. Not verified for this named route. Provider values, app labels and successful runtime behavior are different layers; the audit is not a generation test.

Are these prices what EZ Ai Assist charges?

Public provider or hosting API reference prices in USD, not EZ Ai Assist subscription prices or app charges. Check the app for your current plan, allowance and charge before generating. Pricing is unresolved until the final model mapping is confirmed. Ray 1.6, Ray 2 and Ray Flash 2 prices must not be relabeled as Ray 1.5 prices.

Is this model available or retired?

The owner audit reports lumaModel: ray2 for the Ray 1.5 card. It may serve Ray 2, but the final handler request has not been verified. This page preserves the older URL and exposes that uncertainty.

Sources & freshness

Check the original references.

Reviewed . Public provider or hosting documentation supports the reference specifications and prices. App behavior is based on the owner-supplied code-audit reports labeled October 9, 2026, not live generation tests. No retirement date is inferred from a missing listing, a legacy name or an unresolved route.

Same provider