Skip to main content
Use the mio CLI for creator-side automation, scripted admin workflows, and quick API exploration from a terminal.

​
Install

On macOS or Linux, install the latest released binary with the official installer: 
curl -fsSL https://raw.githubusercontent.com/Searchie-Inc/mio-cli/main/scripts/install.sh | sh
The installer detects your OS and CPU architecture, downloads the matching GitHub release asset, verifies the SHA-256 checksum when checksum tooling is available, and installs mio into /usr/local/bin. Install somewhere you own with PREFIX: 
curl -fsSL https://raw.githubusercontent.com/Searchie-Inc/mio-cli/main/scripts/install.sh | PREFIX="$HOME/.local/bin" sh
Pin a release with VERSION: 
curl -fsSL https://raw.githubusercontent.com/Searchie-Inc/mio-cli/main/scripts/install.sh | VERSION=0.2.1 sh

​
Update

Release installs can update themselves from the CLI: 
mio update
mio update reruns the official release installer into the directory containing the current executable. Use --version to pin a release, or --prefix to install into another directory: 
mio update --version 0.2.1
mio update --prefix "$HOME/.local/bin"
If you installed from source with go install, update through Go instead: 
go install github.com/Searchie-Inc/mio-cli@latest

​
Authenticate

Interactive users can log in once: 
mio login
For scripts, CI, and agents, set a team API key: 
export MIO_API_KEY=mio_sk_live_xxxxx
The CLI reads credentials in this order: 
--api-key <key> -> MIO_API_KEY -> key stored by mio login

​
API Base

The CLI talks to the production API at https://api.member.dev by default. Override it per command with --api-base <url> or globally with MIO_API_BASE_URL. Current API requests are sent to /api/v1 paths. The backend still accepts older /api paths as a compatibility alias during the alpha period, but /api/v1 is the documented contract.