Skip to main content
The dataerai command-line client lets you authenticate and manage assets — download, upload, and metadata — from a terminal or a script. It’s ideal for large or bulk transfers, pipelines, and browserless environments like HPC clusters. The same binary also powers the transfers behind the desktop app.

​
Install

Install with pip — this bundles the binary for your platform and puts the dataerai command on your PATH:
dataerai-cli targets production; the dataerai-cli-beta / dataerai-cli-dev variants default to those instances. Override any of them with DATAERAI_SERVER.
Or build the binary from source in the cli/ directory:
Make sure the install location (or the built ./dataerai) is on your PATH.

​
Commands

See Authenticate and Commands. To run web-app transfers on your own machine, see Run transfers on your own machine.

​
Point the CLI at your server

The CLI talks to a specific Dataerai deployment. Set it with the --server flag or the DATAERAI_SERVER environment variable, using your deployment’s URL:
The server URL saved at dataerai auth login takes precedence over DATAERAI_SERVER, so once you log in you usually don’t need to pass --server again.

​
Credentials

After you log in, your credentials (access and refresh tokens, expiry, email, and server URL) are stored securely in your operating system’s keychain. On a machine with no keychain available — such as a headless server or CI runner — they fall back to a file at ~/.config/dataerai/credentials with owner-only permissions.
Whether in the keychain or the fallback file, these credentials grant access to your Dataerai account — treat them like any other secret.

​
Next steps

Authenticate

Log in from a browser or with a device code.

Commands

Upload, download, and manage metadata.