Developers | Luminafactory

1

Get into the portal

Sign up, then create or join an organisation. Every later step is scoped to that organisation.

Open the portal

2

Create an application

An application represents the consumer product that will call Luminafactory. Budgets and model allowlists live here.

3

Create an API Key Profile

Business Center → API Key Profiles. Name the profile and associate it with applications. The public api_key (prefix lf_ak_) stays visible. The secret_key (prefix lf_sk_) is shown once — store it in a secrets manager. Regenerating the pair invalidates the old credentials immediately (authorizer cache can linger up to about five minutes).

4

Associate agents

Publish (or sandbox) agents onto that application. Consumer traffic only reaches agents you have attached.

5

Connect integrations

In the portal Integrations hub, connect a data source or tool and attach it to the agents that should use it. Chat and the Direct API then pick up that context at runtime. Use the hub for what is available today — this page does not list connector names.

Do not put Direct API keys or Cognito tokens into IDE or MCP config. Integration secrets stay on the connection, never in chat.

6

Call the Direct API

Production base URL: https://api.luminafactory.com/v1. Send these headers on every request:

x-api-key: lf_ak_…
x-secret-key: lf_sk_…
x-organization-id: <your-org-id>
x-application-id: <your-app-id>

List agents, then send a first chat:

GET  /v1/agents
POST /v1/chat

7

What not to mix

Portal login is for humans in the UI. Direct API keys are for server-to-server. IDE/MCP credentials are not Direct API keys. Keep each credential on the path it was issued for.

First production call today