Skip to main content
The Lightsage CLI lets you create Visibility prompts, inspect prompt opportunities, and manage API Performance resources from your terminal. It uses Lightsage’s public API contract.
The CLI uses API key authentication. It does not require browser login.

Install

Install Lightsage with Homebrew:
Check that the CLI is available:

Authenticate

Create an API key in the Lightsage dashboard.
  1. Open Settings > API Keys.
  2. Click Create API key.
  3. Copy the key when it is shown.
Store the key with the CLI:
The CLI stores secret credentials in your operating system keychain when available. This is the recommended setup for local development because the key persists across terminal and agent sessions. You can also save the key non-interactively:
Check which credential source the CLI is using:
Then verify that the key can authenticate API requests:
For CI, containers, or agent sessions where the keychain is not available, set the key as an environment variable:
Add that export to your shell profile or secret manager if it should persist across sessions. Environment variables take precedence over the keychain. You can also pass the key for one command. This does not save the key:
API keys are shown once. Store the key in your secret manager or shell profile. Do not commit it to your repository.

Command groups

Prompts

Create, list, update, and delete Visibility prompts.

Topics

Create, update, and delete prompt topics.

Actions

List prompt actionables, cited pages, and opportunities.

Eval runs

Start durable eval runs and poll their progress.

API Performance runs

List recent eval runs and retrieve a full run result.

Targets

Discover text models and coding-agent model choices.

Configuration

Read and update models, targets, evals, env vars, and base URL.

Sources

List tracked API Performance sources and their scheduled targets.

Skills

List reusable skill context for API Performance evals.

Eval definitions

Inspect and tune prompts, expected behavior, and run context.

Custom evals

Create higher-level task evals for coding agents.

Starter projects

Manage repositories cloned before agent evals run.

Actions

List, update, refresh, and verify API Performance actions.

Global flags

Status commands

Use status commands to check API availability and authentication. Example health response:
Example auth response:

Reference scope

The CLI Reference covers the current public API scope. For HTTP endpoints, request schemas, and the interactive API playground, see the API Reference. The CLI no longer exposes context, workflows, jobs, leaderboard companies, lower-level /v1/api/* commands, or public brand selectors.

Output

Use --output-format json when you need stable output for scripts:
The default pretty output is optimized for humans and can change between CLI releases.

Troubleshooting