luma is the Luma service entry point for video creation, suitable for turning text concepts, static images, and existing generated clips into dynamic assets that can be further developed. Its practical features are first and last frame control and video extension: you can start from a scene description, organize motion around specified images, and continue generating from existing clips. Results include video links, covers, and task information, making it easy to integrate with asset libraries and content production workflows.
Submit requests to the public API at api.acedata.cloud using the documented parameters, then use the results in your application.
api.acedata.cloudInput parameters and result formats vary by service. Use the public API for this model and follow its guide for generation, task retrieval and editing operations.
The above are the creation and API specifications for the luma entry point and do not represent the full feature set of all native Ray series versions.
In addition to text descriptions, luma can also accept image links for the first and last frames, allowing creation to begin from specific visuals. The first frame establishes the starting composition, while the last frame expresses the ending state; prompts supplement subject actions, environmental changes, and camera intent. Suitable for tasks with existing visual drafts that seek to further explore dynamic expression.
When a generated clip is worth keeping but its content has not yet been fully developed, use extend to continue creating instead of starting over from text. Submit the video's ID or link, then describe the subsequent action; you can also add a last frame to express the ending visual of the next segment. This approach makes it easier to explore different directions for a shot's development in stages.
luma provides controls for aspect ratio, looping, and clarity enhancement, and also supports asynchronous submission and task tracking. Applications can first save the task ID, then query the result or receive callbacks, sending completed video links and thumbnails into an asset list. Especially useful for creative tools that need to continue handling other work while generation is in progress.
Use a product scene image as the first frame, combined with text instructions for display actions, environmental atmosphere, and camera direction, to generate dynamic showcase assets; if an ending composition already exists, provide a last frame as well. The delivered videos and covers can enter a marketing asset candidate library for team selection, then be completed with editing, subtitles, and brand packaging.
Use the starting and ending storyboard images as inputs, explain how people or objects move and how the scene changes, and use the generated result to observe the dynamic expression between two visual states. When the idea needs to be extended, continue creating from the generated clip. Suitable for producing concept previews and shot proposals, rather than directly replacing precise animation production.
For the same idea, select landscape, portrait, or square aspect ratios, and enter prompts and reference images suited to each composition to generate assets for different display placements. Background animations can experiment with loop control; the system saves task status, video links, and thumbnails, making it convenient for editors to review candidate results and organize subsequent deliverables.
If you already have static visual artwork, or want to continue developing motion from a generated clip, luma's first-and-last-frame and extension workflows are better suited to these tasks. If you only have a text concept, you can first create a new video, then add reference images once the visual direction is clear. When choosing, focus on image constraints and segmented creation needs rather than merely comparing model names.
luma is the name of a service entry point and is not equivalent to a fixed version such as Ray2, Ray3, or Ray3.2. If a project explicitly requires multiple keyframes, HDR, or a particular video editing method, choose a product that clearly supports those features; if the core needs are text generation, first-and-last-frame guidance, and continuation of existing clips, you can organize creation around these luma workflows.
For text generation, provide a prompt; for image-to-video, provide start_image_url, optionally with end_image_url. First ensure there is an achievable action between the two images.
Submit action=generate to /luma/videos; for extension, use action=extend and submit a video ID or video URL, then describe the subsequent action.
Save the task_id asynchronously, query /luma/tasks or receive callbacks; save the video ID, link, and cover image in the completed result to facilitate the next extension and asset management.
Start with a first frame of a flower bud and end with a final frame of the flower in full bloom, keeping a fixed close-up, a soft background, and the flower branch and camera position unchanged.
First verify the transition between the first and last frames; when continuing, save video_id or video_url, describe the next action, and do not use task_id in place of the video asset ID.
That is not the naming relationship. luma is the name of the video service entry point and cannot be directly equated with a specific fixed Ray version. When using it, tasks can be organized around text generation, first-and-last-frame control, and video continuation; if you need features exclusive to a particular Ray version, choose a product that explicitly supports those features.
You can provide image links through start_image_url and end_image_url, then use prompt to describe the actions and changes you want to occur in between. You can also start creating with only a first frame. Two images are suitable for expressing the starting and ending states of a shot, but the intermediate process is still generated rather than specified frame by frame.
Set action to extend, provide the video_id or video_url of an already generated video, and enter a prompt for the subsequent content. If you want the continuation to end on a specified image, you can also add end_image_url. Save the new video information returned by each generation to facilitate continued creation and asset management.
loop is used to request a looping video, and enhancement is used to control resolution enhancement; they serve playback mode and visual processing respectively and should not be confused as a single feature. When creating dynamic backgrounds, you can try looping and check the transition effect; enabling enhancement also does not promise a particular fixed output resolution.
No. You can set async=true, obtain task_id first, and then retrieve the status and results through task queries; you can also use callback_url to receive completion notifications. The task ID is used to associate this creation, while the video ID identifies the generated asset; save them separately to avoid mixing them up in subsequent extensions.
Choose a development approach or application suited to this model and follow its setup guide.
↗↗
↗
↗This is only a basic call example. See the full docs for more parameters and advanced usage.
View Docs