Account & Configuration

API Key / AI Access Token Management

The CLI calls this credential a VOLTRA API Key. The Agent workout API calls the same credential an AI Access Token. Current tokens use the form bp- followed by 64 hexadecimal characters. Obtain the token from the Beyond+ mobile app's Cortex beta section; the CLI does not issue or revoke remote tokens.

Command	Options	Notes
`voltra config set-api-key <key>`	`[--force] [--json]`	Save API key locally. Validates against remote by default; `--force` skips validation. Required for device/training commands.
`voltra config show`	`[--json]`	Show whether an API key is configured (masked).
`voltra config clear-api-key`	`[--json]`	Remove the locally stored API key.

voltra config set-api-key "<VOLTRA_API_KEY>"
voltra config set-api-key "<VOLTRA_API_KEY>" --force
voltra --json config show
voltra config clear-api-key

Workout requests send the credential as both X-AI-Access-Token and Authorization: Bearer .... Missing credentials return HTTP 401 / code 40800; invalid or expired credentials return HTTP 401 / code 40801. A backend 40300 response means the AI access-token feature is not enabled for the account or rollout.

Identity & Risk

Command	Options	Notes
`voltra whoami`	`[--api-key <key>] [--json]`	Fetch user info for the current API key. Refreshes `~/.voltra/user-preferences.json`.
`voltra config accept-physical-risk`	`[--json]`	One-time acknowledgement required before `load` can apply force.

voltra whoami
voltra whoami --api-key <API_KEY>
voltra config accept-physical-risk

Account & Configuration