Get Modelverse
Modelverse ships inside the ClikaRT release archives: one archive per platform, carrying the ClikaRT runtime and Modelverse together (the clika-modelverse executable, the library, the public headers, and the CMake packages for both products). Installing ClikaRT installs Modelverse; there is no separate Modelverse download and no second install step. The commands start from the archive you received for your platform and the checksum beside it.
Take the archive matching your platform and the checksum beside it, verify, and extract. The two Linux archives arrive as two numbered pieces that concatenate in order; every other platform's archive is one file, and the checksum always covers the whole archive:
cat ClikaRT_linux_x86_64-0.5.1.tar.xz.00.part \
ClikaRT_linux_x86_64-0.5.1.tar.xz.01.part > ClikaRT_linux_x86_64-0.5.1.tar.xz
sha256sum -c ClikaRT_linux_x86_64-0.5.1.tar.xz.sha256
tar -xf ClikaRT_linux_x86_64-0.5.1.tar.xz
export MODELVERSE_INSTALL_DIR="$PWD/ClikaRT_linux_x86_64-0.5.1"
MODELVERSE_INSTALL_DIR is the extracted directory, the same one the ClikaRT documentation calls CLIKART_BUNDLE_DIR; one directory carries both products. (Windows, in PowerShell: CertUtil -hashfile <archive> SHA256 prints the checksum to compare against the .sha256 file, then tar -xf <archive>.)
License credential
Running a model needs the license credential CLIKA issued for your deployment, because Modelverse runs on the ClikaRT runtime and the runtime runs compute under a license. The credential is the CLIKA1-... text your project's license shows as its license key (Runtime licenses is where it comes from). Set it for the process, as the credential text or as the path of a file holding it:
export CLIKA_RT_LICENSE=CLIKA1-...
"$MODELVERSE_INSTALL_DIR"/bin/clika-modelverse <model> prompt "Hello" --device cpu
bin/clikart-license-init <credential> stores it once under your user account instead, and the variable wins when both are present. Without a valid credential the model commands are refused with the code name LICENSE_FAILED, or LICENSE_EXPIRED for a license past its end date.
The clika_modelverse wheel takes the credential from the Python process's environment the same way. License the runtime is the whole contract for both products.
Per platform, the archive to pick and the check that it runs on your machine:
| OS | Architecture | Archive | Verify with | Notes |
|---|---|---|---|---|
| Linux | x86_64 | ClikaRT_linux_x86_64-<version>.tar.xz, delivered as .00.part + .01.part | bin/clika-modelverse devices | CPU always; CUDA with the NVIDIA driver alone, Vulkan with a Vulkan 1.2 driver |
| Linux | arm64 | ClikaRT_linux_arm64-<version>.tar.xz, delivered as .00.part + .01.part | bin/clika-modelverse devices | CPU · CUDA · Vulkan, as above |
| Windows | x86_64 | ClikaRT_windows_x86_64-<version>.zip | bin\clika-modelverse.exe devices | CPU · Vulkan · CUDA on request |
| Windows | arm64 | ClikaRT_windows_arm64-<version>.zip | bin\clika-modelverse.exe devices | CPU · Vulkan |
| macOS | Apple silicon | ClikaRT_macos_arm64-<version>.tar.xz | bin/clika-modelverse devices | CPU · Metal (ships with macOS) |
| Android | arm64-v8a | ClikaRT_android_arm64-<version>.tar.xz | push the directory to the device, run over adb shell | CPU · Vulkan |
The Linux archives carry both CUDA images, and each image is self-contained: the CUDA runtime and cuBLASLt are inside it, so a CUDA machine needs its NVIDIA driver and nothing else, no CUDA toolkit install and no LD_LIBRARY_PATH. The runtime loads the image the driver serves (a driver of major version 580 or newer serves the CUDA 13 image, an older driver the CUDA 12 image).
Modelverse ships a Python binding of its own, the clika_modelverse wheel, beside the archives and the runtime's clika-runtime wheels (Get ClikaRT covers both). It carries the Python package alone and declares clika-runtime at the matching version as its one requirement, so the runtime wheel goes in first:
pip install ./clika_runtime-0.5.1-cp313-cp313-manylinux_2_28_x86_64.whl
pip install ./clika_modelverse-0.5.1-cp313-cp313-manylinux_2_28_x86_64.whl
The clika-modelverse executable comes from the runtime wheel, which installs it as a console script, and from the archive's bin/. The C++ library ships in the archive only.
Every archive carries modelverse.json at its top level, the manifest naming the ClikaRT build this Modelverse build linked against and the minimum glibc it runs on; a Modelverse paired with any other ClikaRT runtime is refused with a readable error, never undefined behavior. dist.json beside it describes the platform build itself (backends compiled in, library layout).
Accelerators, drivers and hardware are the runtime's: the ClikaRT system requirements are the authority.
Then continue with Quick install, which picks up at the extracted directory.