Skip to main content
Use --profile <name> on supported commands when you have a stored Service Account profile. Run a command family without a subcommand to display its built-in help. For one copy-ready command example per command, continue to CLI examples.

Identity availability

A human PAT can use every API-backed command below when RBAC permits it. Local commands such as login and generate do not require API authorization. A Service Account can use only:
The CLI rejects every other command before making an SDK or API call. RBAC can still deny a command from this list when the Service Account lacks the required custom-role permission or project access.

Core record commands

generate only returns locally generated fields. new generates, encrypts and stores them. set updates a matching record or creates it when human mode has enough information.

Project commands

Record management commands

Project audit scope requires both --scope-type project and --scope-id.

Gateway commands

Discovery and lifecycle:
Gateway tokens:
Settings and credentials:
Observability:
Provider credentials and OpenTelemetry headers are read from named environment variables. Their values do not belong in command arguments.

Service Account metadata commands

The public CLI does not create, pause, reactivate, delete, provision, rotate or revoke Service Account credentials.

Argument rules

  • Values in angle brackets are required. Values in square brackets are optional.
  • UUID arguments must be complete IDs. Names are not accepted where an ID is required.
  • --account selects account context. It does not add permissions.
  • --project limits an operation to one project.
  • --profile selects a stored Service Account profile for commands that support machine identity.
  • Repeat --field key=value and --credential <id> when you need more than one value.
  • Use null only where the command syntax explicitly accepts it. It clears the stored optional value.
  • Use none only where documented. It replaces a list with an empty list.
  • Boolean flags accept only true or false.
Run a command family without a subcommand to see the installed version’s exact syntax:

Output

Normal commands write formatted JSON to stdout. Scripts should read stdout as JSON and use the process exit status to decide whether the operation completed. Diagnostic text and stable error codes go to stderr. Commands that return no resource print { "ok": true }.
One-time values, including newly created gateway tokens, are printed once. Redirect them only into an approved custody process. Do not write them to a shared terminal log.

Complete workflow examples

Create and inspect a project:
Create a record without putting its secret value in command history:
Read metadata, then inject decrypted values only into a child process:
Change safe metadata and review immutable history:
Share a record, then revoke the same grant:
Create a provider credential from an environment variable, then create a gateway:
Create a short-lived gateway token and inspect usage without reading stored bodies:
Read safe Service Account metadata as a human:
Run the supported read-only subset with an active Service Account profile:

CLI failures

The CLI never treats an incomplete Service Account profile as a human login. Fix the profile instead of adding a human PAT to the same machine configuration.