mka1 is the official command-line interface for the MKA1 API.
Every operation you can call through the REST API is available as a command, with flags, stdin piping, multiple output formats, and an interactive command explorer.
Use it to:
- Script one-off API calls and CI jobs without bringing in an SDK.
- Inspect live data quickly — list responses, download files, search a vector store.
- Prototype request bodies before porting them into the TypeScript, C#, or Python SDK.
Install
The install script is the quickest way to getmka1. It detects your platform, downloads the matching build, verifies its checksum, and installs mka1 into a directory on your PATH.
MKA1_INSTALL_DIR to choose the install directory, and MKA1_VERSION to pin a specific version instead of the latest.
To install by hand, pre-built binaries for every supported platform are served from downloads.mka1.com. Files under latest/ always hold the newest release, so you can reference them in scripts and CI.
Every file is named
mka1_<os>_<arch>.<ext>. To pin a release, use https://downloads.mka1.com/mka1-cli/v<VERSION>/mka1_<os>_<arch>-v<VERSION>.<ext> instead.
macOS
arm64 for x86_64 on Intel Macs.
Linux
x86_64 for arm64 on 64-bit Arm machines. The i386 builds ship as .deb and .rpm packages only.
Windows
Downloadmka1_windows_x86_64.zip, extract it, and add the folder containing mka1.exe to your PATH. Use the arm64 or i386 zip if that matches your machine.
Verify a download
Every release directory publishes aSHA256SUMS file covering each asset in that release. Run the check from the folder that holds your download:
sha256sum -c in place of shasum -a 256 -c. The install script performs this check for you.
For automation, latest/manifest.json reports the current version along with every asset’s URL, size, and SHA-256.
Verify the install
Print the CLI version to confirm the binary is on yourPATH:
--help, which prints a description, usage, and the flags that apply:
Enable shell completion
Completions are generated on demand and cover subcommands, flags, and known enum values.Run your first request
Authenticate once, then call any endpoint. The quickest path is to set your key in an environment variable and generate a response:Explore interactively
mka1 explore launches a terminal UI that lets you browse every command group, inspect each command’s flags, and execute it without leaving the shell:
Next steps
- Authenticate the CLI — configure credentials and end-user identity.
- Commands — a tour of the command groups with worked examples.
- Pass request bodies — mix individual flags,
--body, and stdin. - Format and filter output — switch between JSON, YAML, table, and TOON, and transform results with jq.
- Debug and inspect — preview requests with
--dry-run, trace them with--debug, and enable agent mode.