Luma Labs
for LuumenAI

Run Luma image and video jobs, and track their files, from the terminal

Connect Luma Labs and your team can see what a generation is doing without opening a browser. Check job state, failure details, and output URLs. List the files in the account, newest first, and inspect ingest or moderation state. Submitting a paid image or video job, or deleting a file, is previewed and held for approval first.

The Luma Labs toolbox

11 tools: 3 read, 8 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadGet FileGet a Luma file's metadata and current ingest, moderation, or deletion state.
  • ReadGet GenerationGet the current state, failure details, and output URLs for a Luma generation.
  • ReadList FilesList files in the connected Luma account, newest first, with optional state and purpose filters.
  • WriteDelete FileSoft-delete a Luma file so new generations cannot reference it. Approval by default
  • WriteEdit ImageSubmit a paid, asynchronous Luma image-edit job. Approval by default
  • WriteEdit VideoSubmit a paid, asynchronous Ray 3.2 video-edit job. Approval by default
  • WriteExtract Image LayersSubmit a paid, asynchronous Luma image layer-extraction job. Approval by default
  • WriteGenerate ImageSubmit a paid, asynchronous Luma image generation job. Approval by default
  • WriteGenerate VideoSubmit a paid, asynchronous Ray 3.2 video generation job. Approval by default
  • WriteReframe VideoSubmit a paid, asynchronous Ray 3.2 video-reframe job. Approval by default
  • WriteUpload FileDirectly upload file bytes to Luma and return the file ID, metadata, and current upload/ingest state. Approval by default

One prompt, start to finish

What a governed Luma Labs run looks like inside Luumen.

Questions

How does LuumenAI connect to Luma Labs?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Luma Labs on its own?

Read actions answer immediately. Anything that writes — delete file, edit image, edit video, extract image layers, and more — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Luma Labs — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put Luma Labs to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.