List Apps
const url = 'https://agents.lumalabs.ai/v1/apps?envelope=false';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://agents.lumalabs.ai/v1/apps?envelope=false' \ --header 'Authorization: Bearer <token>'Every workflow app this client's team may run that is offered to partners and has an active release.
An empty list for a team with no entitlements — never an error, and never a hint of what else exists.
Authorizations
Section titled “Authorizations”Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters”Return the catalog as a page, {data, has_more, next_cursor}, like every other list. The bare array is the default until GA, when the page becomes the default.
Return the catalog as a page, {data, has_more, next_cursor}, like every other list. The bare array is the default until GA, when the page becomes the default.
Responses
Section titled “ Responses ”Successful Response
One entitled app, as its partner sees it: identity, the document it produces, the renderer that reads it, and what is live right now.
Everything that makes the app what it is — its compiled spec, skills, tool prompts, rubric — stays server-side. A partner runs the app by naming it.
object
Which release of an app a partner's next session would run. With no release active, an app may serve the package shipped in Luma's code instead; this then describes that package.
Kit registry key for this app's plan artifact. Defaults to schema_ref; select registry[renderer_key] ?? registry['default'] so an app sharing another's document schema can still ship its own surface.
The plan-artifact schema this app's sessions produce.
The partner app catalog as a page (GET /v1/apps?envelope=true).
Every app has an active release, so the catalog fits on one page today:
has_more is false and next_cursor null until it does not.
object
One entitled app, as its partner sees it: identity, the document it produces, the renderer that reads it, and what is live right now.
Everything that makes the app what it is — its compiled spec, skills, tool prompts, rubric — stays server-side. A partner runs the app by naming it.
object
Which release of an app a partner's next session would run. With no release active, an app may serve the package shipped in Luma's code instead; this then describes that package.
Kit registry key for this app's plan artifact. Defaults to schema_ref; select registry[renderer_key] ?? registry['default'] so an app sharing another's document schema can still ship its own surface.
The plan-artifact schema this app's sessions produce.
Example
{ "has_more": false}Validation Error
object
object
object
Examplegenerated
{ "detail": [ { "ctx": {}, "input": "example", "loc": [ "example" ], "msg": "example", "type": "example" } ]}