Authentication

Configure the Saber CLI with an API key, verify login state, and understand how local credentials map to Saber access.

The Saber CLI authenticates with the same API keys used by the public REST API. Create a key in Saber, then save it locally for CLI use.

saber auth login

For non-interactive setup, pass the key directly:

saber auth login --key sk_live_...

Verify your session

saber auth status

Use status before automation or agent workflows so failures are caught before a long-running command starts.

Logout

saber auth logout

Logout removes the stored CLI credential from the machine. It does not revoke the API key in Saber. Revoke or rotate keys from the Saber API Keys page when a key should stop working everywhere.

CI and automation

Use SABER_API_KEY or your CI secret manager for jobs that should not write credentials to disk:

export SABER_API_KEY="sk_live_..."
saber credits --json

Avoid printing signal output in shared logs when the results contain prospect, customer, or CRM context.

Agent context

If you use Claude Code with Saber Skills, run:

saber init-claude

init-claude writes Saber organization context and command guidance into CLAUDE.md, so Claude Code can use Saber Skills with the right profile, connector status, available commands, and credit guardrails.

On this page