Skip to main content

VIZO CLI

vizo is the command-line tool for downloading the datasets you are licensed for on the VIZO platform. It needs Python 3.9 or newer and nothing beyond the standard library.

Install

python3 -m venv ~/vizo-venv            # Python 3.9 or newer; the one macOS ships is fine
source ~/vizo-venv/bin/activate
pip3 install vizo

Use

export VIZO_API_KEY=vz_sk_live_...     # from the API Keys page; the only way to authenticate

vizo datasets                          # what you can download, and where to request access
vizo download ego4d -o ~/vizo-data/ego4d --parts clips annotations --benchmarks FHO --dry-run
vizo download ego4d -o ~/vizo-data/ego4d --parts clips annotations --benchmarks FHO -y
vizo verify ~/vizo-data/ego4d --checksum

python3 -m vizo works the same as vizo.

download accepts the official selectors (--parts/--datasets, --uids/ --video_uids, --uid-file, --universities, --benchmarks, --splits, --views, --metadata), plus --shard N/M for splitting one download across machines, --workers, --dry-run, -y, and --refresh-manifest. A dry run fetches nothing but does create the output folder and save the manifest in it, so the real run that follows targets the same release. Files land in the official layout under -o; .vizo/ inside it holds the saved manifest, a log and a done-record per run. Rerunning the same command skips completed files; a file that was interrupted starts again from its beginning. Interrupted or failed downloads leave *.part files, which a run and verify report and never delete (shards may share a folder); delete them when no run is using the folder.

Exit codes: 0 done · 1 usage · 2 key problem · 3 not entitled · 4 incomplete/unreachable.

The full guide is on the VIZO platform, signed in, under Develop → CLI (https://vizo-platform.vercel.app/docs/cli): installation, API keys, choosing what to download, each dataset's parts and layout, verifying, large and sharded downloads, a command reference and troubleshooting. Its source is docs/ in the source repository; working on the CLI itself is covered in DEVELOPMENT.md there.

Metadata

Release files for vizo 0.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for vizo 0.0.1
File Size Uploaded Provenance Actions
vizo-0.0.1.tar.gz 34.9 kB With provenance Details for vizo-0.0.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for vizo 0.0.1
File Interpreter ABI Platform Actions
vizo-0.0.1-py3-none-any.whl Python 3 none any Details for vizo-0.0.1-py3-none-any.whl

Total release size: 73.6 kB

Release files / vizo-0.0.1.tar.gz

Download URL vizo-0.0.1.tar.gz
Size 34.9 kB
Tags Source
SHA-256 checksum
How to use checksums
4f4a560e8f981f95f7e8bfd69c8e6ed3f1fdc4140b07e99e1d501362faf55e17
BLAKE2b-256 checksum
How to use checksums
f0cf65757354b2ab0b6b02d34488b82ae08f9b555cc05f33b6e26964cbd7966f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.

Transparency log

Release files / vizo-0.0.1-py3-none-any.whl

Download URL vizo-0.0.1-py3-none-any.whl
Size 38.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
40e5819c1a4a5ab3be007c1de72fccaaf6fb139386ab65be2062056a3dae4434
BLAKE2b-256 checksum
How to use checksums
d1a2af63e0dec81689bb3b25d657761c661978d38f47357554fbe617229bc069
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.

Transparency log

Security for vizo 0.0.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for vizo-0.0.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page