Environment variables

Core

Variable	Config option	Needed for
`A2A_URL`	`a2aUrl`	Chat. Usually `<NEBULAS_API_URL>/v1/orchestrator/a2a`.
`NEBULAS_API_URL`	`nebulasApiUrl`	Forms, branding, project lookup.
`NEBULAS_API_KEY`	`nebulasApiKey` and each handler’s `apiKey`	Sent as `x-api-key`.
`NEBULAS_PROJECT_ID`	`nebulasProjectId`	Where conversations are recorded.
`NEBULAS_AUTH_STRATEGY`	`nebulasAuthStrategy`	`session`, `client_credentials`, `resource_owner_password`, `service_account`.
`AUTH_PROVIDER`	`authProvider`	`auth0` or `entra`.

Service account

Variable	Config option
`SERVICE_ACCOUNT_ID`	`serviceAccount.serviceAccountId`
`SERVICE_ACCOUNT_KEY_ID`	`serviceAccount.keyId`
`SERVICE_ACCOUNT_PRIVATE_KEY`	`serviceAccount.privateKeyPem` (`\n` escapes allowed)
`SERVICE_ACCOUNT_PRIVATE_KEY_PATH`	`serviceAccount.privateKeyPath`
`SERVICE_METADATA_ORG_ID`	`serviceAccount.metadata.org_id` (only with `sendMetadata: true`)
`SERVICE_METADATA_URL`	`serviceAccount.metadataUrl`

Auth0

Variable	Config option
`AUTH0_DOMAIN`	`auth0.domain`
`AUTH0_CLIENT_ID`	`auth0.clientId`
`AUTH0_CLIENT_SECRET`	`auth0.clientSecret`
`AUTH0_A2A_AUDIENCE`	`auth0.audience`
`AUTH0_ROP_USERNAME`	`auth0ServiceUser.username`
`AUTH0_ROP_PASSWORD`	`auth0ServiceUser.password`

Microsoft Entra ID

Variable	Config option
`ENTRA_TENANT_ID`	`entraService.tenantId`
`ENTRA_CLIENT_ID`	`entraService.clientId`
`ENTRA_CLIENT_SECRET`	`entraService.clientSecret`
`ENTRA_CLIENT_CERTIFICATE` / `_PATH`	`entraService.certificatePem` / `certificatePath`
`ENTRA_CLIENT_PRIVATE_KEY` / `_PATH`	`entraService.privateKeyPem` / `privateKeyPath`
`ENTRA_A2A_SCOPE`	`entraService.scope`, often `api://<app-id>/.default`
`ENTRA_OBO_CLIENT_ID`, `ENTRA_OBO_CLIENT_SECRET`, `ENTRA_OBO_SCOPE`	`entraObo.*` for On-Behalf-Of

Branding

Variable	Config option
`NEBULAS_BRAND_NAME`	`nebulasBrandName`
`NEBULAS_BRAND_MODULE_ID`	`nebulasBrandModuleId`