---
title: Get Modelverse
description: Pick your platform's ClikaRT archive; Modelverse ships inside it, with the download and verify commands.
---

Modelverse ships inside the ClikaRT release archives: one archive per platform, carrying the ClikaRT runtime and Modelverse together (the `clikart-cli` 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 archive comes from your CLIKA Platform deployment: [Download the ClikaRT SDK](/platform/how-to/download-the-clikart-sdk) covers the web dialog, the platform CLI and the MCP tools that hand it out, with the license key the runtime needs beside it. The commands start from that archive and the checksum shown with it.

The archive comes from the CLIKA platform's **Download ClikaRT** dialog, the platform CLI (`clika-cli runtime-sdk download`) or the MCP tools ([Download the ClikaRT SDK](/platform/how-to/download-the-clikart-sdk) walks each surface); the dialog shows the archive's SHA-256 beside its download button. The release the dialog offers is the deployment's own pin, which may differ from the release these pages are written for (`0.6.4`); a download's own `README.md` is the authority for the release it came from, its commands and file names included. Take the one file for your platform, check it against that digest, and extract:

```bash
echo "<sha256>  ClikaRT_linux_x86_64-0.6.4.tar.xz" | sha256sum -c
tar -xf ClikaRT_linux_x86_64-0.6.4.tar.xz

export MODELVERSE_INSTALL_DIR="$PWD/ClikaRT_linux_x86_64-0.6.4"
```

`MODELVERSE_INSTALL_DIR` is the extracted directory, the same one the ClikaRT documentation calls `CLIKART_BUNDLE_DIR`; one directory carries both products. (macOS checks with `shasum -a 256 -c` over the same line. Windows, in PowerShell: `(Get-FileHash <archive>).Hash -eq "<sha256>"`, 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](/platform/concepts/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:

```bash
export CLIKA_RT_LICENSE=CLIKA1-...
"$MODELVERSE_INSTALL_DIR"/bin/clikart-cli <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.

From Python, `clika_runtime.modelverse` takes the credential from the process's environment the same way. [License the runtime](/clikart/how-to/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` | `bin/clikart-cli devices` | CPU always; CUDA with the NVIDIA driver alone, Vulkan with a Vulkan 1.2 driver |
| Linux | arm64 | `ClikaRT_linux_arm64-<version>.tar.xz` | `bin/clikart-cli devices` | CPU · CUDA · Vulkan, as above |
| Windows | x86_64 | `ClikaRT_windows_x86_64-<version>.zip` | `bin\clikart-cli.exe devices` | CPU · Vulkan |
| Windows | arm64 | `ClikaRT_windows_arm64-<version>.zip` | `bin\clikart-cli.exe devices` | CPU · Vulkan |
| macOS | Apple silicon | `ClikaRT_macos_arm64-<version>.tar.xz` | `bin/clikart-cli 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).

From Python, Modelverse ships inside the runtime's `clika-runtime` wheel as `clika_runtime.modelverse` ([Get ClikaRT](/clikart/getting-started/get-clikart#python-wheels) picks the wheel for your machine), so one install gives both:

```bash
pip install ./clika_runtime-0.6.4-cp313-cp313-manylinux_2_28_x86_64.whl
python -c "import clika_runtime.modelverse as mv; print(mv.__version__)"
```

The subpackage loads the runtime before its own extension, and a runtime and a model library from different releases refuse to import, naming both versions. The `clikart-cli` executable comes from the same 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 `dist.json` at its top level, which describes the platform build itself (the target it serves, the backends inside, the library layout), and `VERSION`, the release it belongs to. The runtime and the model library in one archive are built together; a model library paired with a runtime of another release is refused with a readable error naming both versions, never undefined behavior.

Accelerators, drivers and hardware are the runtime's: the [ClikaRT system requirements](/clikart/system-requirements) are the authority.

Then continue with [Quick install](installation.md), which picks up at the extracted directory.