Sanaf AI
Start free
Artificial Intelligence

Luma Labs, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Luma Labs account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Artificial Intelligence
  • Connects with a key
  • 11 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Luma Labs is

Create and manage AI image and video generations and reusable files through the current Luma Agents API.

You paste in a key from your own Luma Labs account. It is kept encrypted, and you can withdraw it from inside Luma Labs whenever you like.

How a run works

One message in, the work done in Luma Labs.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Luma Labs. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Luma Labs account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

11 tools it already has

What it can do in Luma Labs

These are the ready-made tools your AI employee already has in Luma Labs. It is not limited to them, but it never has to be taught these.

  • Delete FileSoft-delete a Luma file so new generations cannot reference it. The file's metadata remains retrievable with state=deleted.
  • Edit ImageSubmit a paid, asynchronous Luma image-edit job. Returns immediately; use GETGENERATION with generationid to monitor it.
  • Edit VideoSubmit a paid, asynchronous Ray 3.2 video-edit job. Returns immediately; use GETGENERATION with generationid to monitor it.
  • Extract Image LayersSubmit a paid, asynchronous Luma image layer-extraction job. Pricing is flat per generation at the selected resolution, regardless of layer count; use GETGENERATION with generation
  • Generate ImageSubmit a paid, asynchronous Luma image generation job. Returns immediately; use GETGENERATION with generationid to monitor it.
  • Generate VideoSubmit a paid, asynchronous Ray 3.2 video generation job. Returns immediately; use GETGENERATION with generationid to monitor it.
  • Get FileGet a Luma file's metadata and current ingest, moderation, or deletion state. Soft-deleted files remain retrievable with state=deleted.
  • Get GenerationGet the current state, failure details, and output URLs for a Luma generation.
  • List FilesList files in the connected Luma account, newest first, with optional state and purpose filters. Returns one page and a cursor for continuation.
  • Reframe VideoSubmit a paid, asynchronous Ray 3.2 video-reframe job. Returns immediately; use GETGENERATION with generationid to monitor it.
  • Upload FileDirectly upload file bytes to Luma and return the file ID, metadata, and current upload/ingest state.
Access, and who is in charge of it

You stay the boss of your Luma Labs account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Luma Labs account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Luma Labs is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Luma Labs and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Luma Labs

Can an AI employee really work inside Luma Labs?
Yes. It signs in to your own Luma Labs account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Luma Labs?
No. Nothing moves and nothing is replaced. Your records stay in Luma Labs, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Luma Labs account?
You paste in a key from your own Luma Labs account. It is kept encrypted, and you can withdraw it from inside Luma Labs whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Luma Labs?
It has 11 ready-made tools in Luma Labs today, among them Delete File, Edit Image and Edit Video. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Luma Labs and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Luma Labs and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Luma Labs?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Luma Labs is written down with what it did and when.