Enterprise API access
The article below is a general overview. For the most up to date information, please visit: https://docs.agents.lumalabs.ai
Enterprise API access now lives directly inside Luma Agents. Enterprise admins can generate API keys from Luma Agents Settings. You don't need a separate signup, API account, or contract.
Previously, Luma Agents and the Luma API were separate products, so enterprise customers couldn't use one contracted credit pool across both. Now the Agents app and the API run on the same enterprise setup.
What carries over to the API?
The API uses the enterprise configuration you've already set up in Luma Agents, including:
Existing credits: Your contracted credits work across both the Agents app and the API.
Teams and sub-teams: API usage follows your existing team structure.
Permissions and admin controls: Access stays managed in one place.
Model configuration: Model settings made for your organization apply to the API.
Why does this matter?
Shared credits: Use the same contracted credits across the Agents app and the API instead of managing separate pools.
Shared controls: Team allocation, admin permissions, and model configuration stay in one place.
More flexibility: Creative teams can keep working in Luma Agents while engineering teams build custom API workflows, all under the same enterprise setup.
1. Generating an API Key
Who can create API keys?
Only enterprise admins can create API keys. If you don't see the Developer tab or the API keys controls in Settings, check with your organization's admin to confirm your role.
How do I create an API key?
Open Settings in Luma Agents.
Go to the Developer tab and select API keys.
Create a new key and give it a clear, recognizable name (for example, marketing-automation or production).
Tip: Descriptive key names make it much easier to track usage later, especially when several teams or workflows use the API.
2. How API Usage Is Charged
API usage follows the same credit structure already set up for your organization. Where credits are drawn from depends on how your teams are organized:
Team structure | Key assignment | Where usage is charged |
|---|---|---|
Organization with sub-teams | Every API key must be assigned to a specific sub-team | That sub-team's allocated credits. Keys can't spend credits at the parent-organization level. |
Single-level team | No sub-team assignment needed | The team's overall credit balance, the same balance used in the Agents app |
3. Tracking and Managing API Keys
How do I see how many credits each key is using?
Open the Usage page and view the Boards / API keys breakdown to see credits consumed by each key.
Can I rename a key?
Yes. Admins can rename keys at any time to keep your API environment organized.
How do I turn off a key?
Admins can deactivate a key at any time. Once a key is deactivated, it stops working immediately.
4. Spending and Key Security
Do API keys have their own spending limit?
No. API keys don't have an individual spending cap. Anyone holding a key can use credits up to the available balance of the team (or sub-team) the key belongs to.
How should we manage keys safely?
Share keys carefully: Only give keys to the people and systems that need them, and avoid sharing them broadly inside your organization.
Monitor usage regularly: Check the Usage page to review consumption by key.
Deactivate when needed: If a key is no longer needed, or you see unexpected usage, deactivate it right away.
5. API vs. the Luma Agents App
Should my team use the Agents app or the API?
Both use the same enterprise environment, but they're built for different users:
Luma Agents app | Luma API | |
|---|---|---|
Who it's for | Most users | Power users and engineering teams |
Experience | Generation, status tracking, and outputs are handled in the app | Direct access to the model, with no agent instructions layered in |
Best for | Everyday creative work | Exact model selection, custom workflows, and high-volume parallel generations |
Skills required | None | Coding knowledge and familiarity with API calls |
In short: Luma Agents is the easiest way to create. The API gives you the deepest level of programmatic control. Most creative users will want to stay in Luma Agents, which handles the complexity for you. Teams that need direct model access or custom programmatic workflows can use the API, and both groups work from the same credits, team structure, and admin settings.
6. Quick Answers
How do I get API access? An enterprise admin can create a key in Settings → Developer → API keys.
We have sub-teams. How does that work? Each key must be assigned to a sub-team and uses that sub-team's credit allocation.
Is there a limit per key? No. A key can spend up to the available credit balance of its team or sub-team.
Need help?
For API technical questions, see the API FAQ or email support+luma-agents-api@lumalabs.ai.