Skip to main content
The CLI authenticates with a partner API key. On a workstation, reactor auth login creates that key for you in the browser. In CI, get a key from the dashboard and set it in the environment.

​
Interactive (macOS / Linux workstation)

reactor auth login opens your browser on reactor.inc and waits for you to approve the login.
Check that the confirmation code in the browser is the same as the code in your terminal. When the two codes are different, do not approve the login.
Approval creates a new API key for this machine. The key is stored in the system keychain (macOS Keychain or Linux Secret Service). Non-sensitive metadata (account ID, server URL) is saved to ~/.reactor/config.yaml. When you run reactor auth login again and the stored key still works, the CLI keeps it and tells you that you are already authenticated.

​
Other ways to log in

Some machines have no browser of their own, such as a host you reach over SSH. Use --no-browser there, then open the printed URL on another device:

​
Non-interactive (CI/CD, headless Linux, Docker)

Set REACTOR_API_KEY in the environment:
When REACTOR_API_KEY is set it takes precedence over the system keychain. reactor auth login becomes a no-op (it prints an informational message and exits without prompting or writing to the keychain).

​
Check status

Sample output:
The Key source: line tells you whether the key came from the environment or the keychain.

​
Log out

reactor auth logout removes the stored credentials from the machine: the keychain entry and the cached account metadata in ~/.reactor/config.yaml. If REACTOR_API_KEY is set, the command warns you to unset it, because the environment variable keeps authenticating the shell. When the key came from a browser login, logout also revokes it on the server, so it stops working on every machine. Revocation is best effort. When it fails, the CLI prints a warning and still clears the local credentials.

​
Server override

The default server is https://api.reactor.inc. Override per-invocation with --server <url>, or persistently with REACTOR_SERVER=<url> in the environment.

​
Next

Register a model

Provision a model record on the platform.

Publish a release

Build the image and upload weights in one command.