Installation guide

Install QZX without fighting your Python environment

Choose an installation path that matches how you use Python. Keep QZX isolated as a standalone CLI with pipx, or install it with pip inside an environment you intentionally control.

QZX — Quick Zap Exchange is free and open source, created and maintained by Alejandro Sánchez. The current published package is 0.2.2.0.7 and declares Python >=3.11.

Choose an installation path Continue to the AI-agent quickstart

Choose by environment

Three honest ways to start

Standalone CLI

Keep QZX isolated with pipx

Use this when QZX is a command-line application on your machine rather than a dependency of a Python project. pipx gives the app its own environment while exposing the qzx command on your PATH.

pipx install qzx

Controlled Python environment

Use pip where you own the environment

An activated virtual environment or another Python environment you deliberately manage is a valid place for QZX. The published-channel command below remains supported.

python -m pip install --upgrade qzx

Evaluate first

Try the published CLI without keeping it

If pipx is already available, run QZX in a temporary isolated environment and ask the runtime to identify itself. This is useful when you want evidence before deciding to install.

pipx run --spec qzx qzx version

Verify the runtime

Turn installation into a first success

Do not assume an installer succeeded because it printed no obvious error. Ask the installed runtime for its identity, then complete QZX's canonical read-only first success.

qzx version --json
qzx getCurrentDateTime --output-format iso --json

Once that works, the AI-agent quickstart turns the installation into a useful project-inspection workflow. The installed runtime remains the source of truth for its own version and command catalog.

If pip says externally-managed-environment

Respect the managed Python boundary

Some operating systems and package managers protect their base Python installation. That message means the base interpreter is not the right target for an ordinary application install.

Do not work around it with sudo pip, --break-system-packages, by deleting an EXTERNALLY-MANAGED marker, or by changing ownership of managed Python directories. Install pipx using your platform's supported method, then run pipx install qzx.

Official pipx installation guide QZX Python and platform evidence

Keep control later

Update or remove the isolated CLI cleanly

A pipx installation remains separately manageable instead of becoming an invisible dependency of another project.

pipx upgrade qzx
pipx uninstall qzx

If qzx is not visible after installation, run pipx ensurepath and follow pipx's instruction to refresh or reopen the shell.

Distribution boundary

Use published channels, not an imagined binary

QZX currently publishes its end-user Python package on PyPI. Native standalone Windows executables, macOS application bundles, Homebrew formulae, and Linux distribution packages are not currently advertised as official QZX release channels. Check releases for exact published artifacts and compatibility for current platform evidence.

Prefer the source-level installation document? The GitHub installation guide records the same public boundary alongside the code.