Status

Your deployment’s health

Your deployment reports the health of each of its components and connectors to LightHouse: the gateway, the orchestrator, jobs and each connector, as ok, degraded or down, with a fixed detail code.

See it in LightHouse, or read it:

curl "https://$AAL_TENANT.atlanticagenticlabs.com/api/v1/health" \
  -H "Authorization: Bearer $AAL_KEY" \
  -H "CF-Access-Client-Id: $CF_ACCESS_CLIENT_ID" \
  -H "CF-Access-Client-Secret: $CF_ACCESS_CLIENT_SECRET"

import os

import httpx

headers = {
    "Authorization": f"Bearer {os.environ['AAL_KEY']}",
    "CF-Access-Client-Id": os.environ["CF_ACCESS_CLIENT_ID"],
    "CF-Access-Client-Secret": os.environ["CF_ACCESS_CLIENT_SECRET"],
}
print(httpx.get(f"https://{os.environ['AAL_TENANT']}.atlanticagenticlabs.com/api/v1/health",
                headers=headers).json())

const res = await fetch(`https://${process.env.AAL_TENANT}.atlanticagenticlabs.com/api/v1/health`, {
  headers: {
    Authorization: `Bearer ${process.env.AAL_KEY}`,
    "CF-Access-Client-Id": process.env.CF_ACCESS_CLIENT_ID!,
    "CF-Access-Client-Secret": process.env.CF_ACCESS_CLIENT_SECRET!,
  },
});
console.log(await res.json());

The MCP tool health returns the same. See Health for what each check means, and the Health reference.

Because the engine runs in your account, most of what can go wrong with your agents is visible in your own cloud’s monitoring first. LightHouse being unreachable does not stop your engine: telemetry is buffered in your account and sent when LightHouse is back, and approvals wait rather than proceed.

LightHouse’s own status

A public status page for LightHouse and its sign-in: Coming

Until it exists, ask us about LightHouse’s own status as described in Support.

Incident notices

Published incident notices, with a timeline and what was done: Coming