Install and Verify the CLI

The invite-only disposable DEV beta has a public installer for its current CLI artifact. There is no mutable release feed, and the installer never uses a latest path or silently falls back to a legacy artifact.

Install the current source-bound release

Download the installer from its stable public URL, review it, and run it:

curl --disable --fail --silent --show-error --location \
  --proto '=https' --proto-redir '=https' \
  --output install.sh \
  https://releases.zerokie.com/install.sh
sh install.sh

When INSTALL_DIR is unset, the installer creates and uses XDG_BIN_HOME when set, otherwise $HOME/.local/bin. It never invokes sudo or doas. If the selected directory is not on PATH, the installer prints a note; add that directory to your shell path before running zerokie.

The installer detects Linux or Darwin on amd64 or arm64. It resolves to the current immutable source-bound release, downloads only that target, and checks the bytes against its embedded SHA-256 before installation. It stops on a download, checksum, installation, or version-execution failure.

The current release is version ddb02202, built from source commit ddb02202bef7d488f88fd2d9c67e9db6ff8e379be54c59b21de5ddcb4bdbdb6f at 2026-07-28T08:51:51Z. Its immutable manual-download base is:

https://releases.zerokie.com/releases/ddb02202bef7d488f88fd2d9c67e9db6ff8e379be54c59b21de5ddcb4bdbdb6f/

Manual downloads must stay under that full-source-SHA base and must be checked against the target-specific SHA-256 recorded by the current release contract. Do not execute mismatched bytes or search for another artifact.

Mint and copy a token

After the operator authorizes your verified OIDC email, sign in through OIDC and let first-login provisioning create the customer record. Open Tokens, mint a customer token, and copy it from the one-time plaintext view. The plaintext is not shown again.

Log in to the explicit endpoint

Replace the placeholder. The endpoint must be the exact HTTPS API endpoint provided for this DEV authorization:

zerokie login --endpoint <DEV_API_HTTPS>

At the Token: prompt, paste the copied token with hidden input from an interactive terminal. Do not put the token in command arguments.

Never put a real token in documentation, source control, a URL, or shared output. Continue with the first static deploy.