CLI automation and output

The CLI prints readable tables to a terminal and JSON when output is piped, so the same command works interactively and in automation.

aiglot batches list                    # table on a terminal
aiglot batches list | jq '.data[0].id' # JSON when piped
aiglot batches list --output ndjson    # one object per line
aiglot account --json                  # explicit JSON

Failures go to standard error. Standard output therefore remains safe to pipe into another program.

CI authentication

Create a dedicated, minimum-scope API key and store it in the CI provider’s secret manager:

export AIGLOT_API_KEY="aig_live_…"
aiglot account --json

The CLI checks credentials in this order: AIGLOT_API_KEY, OS keychain, then its protected config file.

Exit codes

Scripts should branch on the exit code or structured error.code, not error-message text.

Retries

The CLI retries 429 and temporary server failures with bounded backoff. Use --no-retry when the caller owns retry policy. Destructive commands never wait forever for an interactive prompt: non-interactive use must pass --force.

Profiles

Use named profiles to keep credentials for different workspaces or environments separate:

aiglot --profile client-a auth login --key "$CLIENT_A_KEY"
aiglot --profile client-a account
export AIGLOT_PROFILE=client-a

Environment variables