ak login

Synopsis

What it does: Authenticate with agentkit-web using a license key device activation, email OTP, or a user API key.

Who it's for: Users installing paid remote kits.

When to use it: Before installing or updating licensed remote kits.

Examples: ak login --license-key ak_license_... --no-interactive ak login --email you@example.com ak login --api-key ak_live_... --no-interactive

What changes on disk: Writes a CLI registry session for email/API-key login or an App device session for license-key activation to ~/.agentkit/auth/session.json. Raw credentials are not persisted.

Output modes: pretty default on TTY (colors, ASCII markers) plain auto when stdout piped or --no-interactive json --json (single-object envelope, NDJSON-safe)

Exit codes: 0 success 1 runtime error 2 invalid flags 3 user-cancel (SIGINT, prompt-cancel)

ak login [flags]

Options

      --api-key string        AgentKit user API key from your web profile
      --device-name string    Device name for --license-key activation (default: hostname)
      --email string          Email address for OTP login
  -h, --help                  help for login
      --json                  Emit machine-readable JSON (implies --no-interactive)
      --license-key string    AgentKit license key for device activation
      --no-interactive        Disable interactive prompts (CI-safe)
  -q, --quiet                 Suppress non-error output on stderr
      --registry-url string   AgentKit registry base URL (default: $AGENTKIT_REGISTRY_URL, then dev/staging https://staging.agentkit.best or release https://agentkit.best)
  -V, --verbose               Extra diagnostic output on stderr (loses to --quiet)
  -y, --yes                   Assume yes for all prompts

Synopsis

Options

SEE ALSO

On this page