Skip to main content
The CLI ships with the Python package:
Browser credentials are stored in your operating system keychain and are never printed. heybee auth logout revokes the credential on HeyBee before removing it locally. Browser authorization asks you to choose a workspace. The resulting credential is permanently scoped to that workspace.

Everyday commands

Add --axis-key <criterion> to result show or result evidence for a single criterion’s decision. heybee huggingface import, list, and status drive dataset imports. Evaluations are created in the workspace bound to the current credential. Use heybee workspace credits <workspace-id>, heybee workspace members <workspace-id>, and heybee workspace invites <workspace-id> to inspect its state. Invitations require confirmation. To use another workspace, run heybee auth login again and select it. Explicit workspace commands are also available for automation:
Creating or revoking a key and connecting or disconnecting a workspace integration require confirmation. Add --yes only after the action has been approved.

Scripting

Add --json to any command for stable machine-readable output. Errors include an error code, HTTP status, and request ID. Pass --idempotency-key on writes you might retry, such as link creation or pause and resume, so a rerun never creates a duplicate. The CLI follows the same feature, role, and quota rules as the app, and interactive use always confirms before anything destructive or paid.

Headless machines

Create an API key under Workspace settings → API keys, then set it on the machine: