PricingAPI keys
  • Overview
  • Quickstart
  • Authentication
  • CLI overview
  • Install and update
  • CLI authentication
  • Command reference
  • Configuration
  • Generation workflows
  • Jobs and media inputs
  • Agent skills
  • Security
  • Troubleshooting

CLI

CLI authentication

Sign the CLI in with the Sume sign-in, or configure an API key for scripts.

sume login signs the CLI in with the same Sume sign-in as the hosted MCP (https://mcp.sume.com). It opens the browser; you sign in and select Allow; the redirect comes back to the CLI on 127.0.0.1, and the CLI stores the sign-in in its local config. Nothing is saved as an API key.

bash
sume login
sume auth status

On a remote or headless machine, sign in with a code. The CLI prints a code and a link; open the link on any device, sign in and approve the code:

bash
sume login --device

sume login --no-browser does the same. If the default callback port is busy, the CLI picks a free one; --port <port> pins one.

The sign-in keeps a one-hour access token and a refresh token. The CLI refreshes the token on its own, and sume logout revokes the sign-in on the server. To call the API from your own script with the sign-in:

bash
curl https://api.sume.com/v1/me \
  -H "Authorization: Bearer $(sume auth token)"

CI, server automation and scripts can still use an API key. Create one in the API Keys dashboard:

bash
sume auth setup --api-key "$SUME_API_KEY"
bash
export SUME_API_KEY="sume_live_..."
export SUME_API_BASE_URL="https://api.sume.com/v1"
export SUME_API_AUTH_MODE="x-api-key"

SUME_API_KEY wins over a stored sign-in. x-api-key is the CLI default for keys; SUME_API_AUTH_MODE=bearer sends the key as Authorization: Bearer.

By default, the CLI stores the local config in ~/.sume-com/config.json, readable only by you.

On this page