The CLI

View as Markdown

ComingThe lighthouse command line is not published yet. There is nothing to install, and no login or other command to run.

Until then

Everything the command line will read is in the API today, with curl or any HTTP client:

To	Use
Check who you are	`GET /api/v1/me`: see the Quickstart
List agents and runs	`GET /api/v1/agents`, `GET /api/v1/runs`: see the Read reference
See spend	`GET /api/v1/usage`, `GET /api/v1/billing/usage`
See limits	`GET /api/v1/limits`
Connect a source	Setup and admin → Connectors in LightHouse: see Connect your estate

Pipe any of them through jq for scripting. Every answer is JSON, and every refusal is {error, message} with a fixed code (Errors), so a CI job can branch on it.

Use in CI

A CI job reads with a machine key and your tenant’s Access service token, held in the CI system’s secret store:

curl -sf "https://$AAL_TENANT.atlanticagenticlabs.com/api/v1/agents?status=failing" \
  -H "Authorization: Bearer $AAL_KEY" \
  -H "CF-Access-Client-Id: $CF_ACCESS_CLIENT_ID" \
  -H "CF-Access-Client-Secret: $CF_ACCESS_CLIENT_SECRET" \
  | jq -e '.items | length == 0'

curl -f fails the job on any refusal; jq -e fails it if any agent is failing. A key never approves or deploys: see Authentication.