verlet
Download and explore Verlet datasets from the command line.
Install
curl -sSL https://raw.githubusercontent.com/verlet/verlet-cli/main/install.sh | bash
This creates an isolated venv at ~/.verlet/venv and symlinks verlet into ~/.local/bin.
Or install manually:
pip install verlet
For development:
git clone https://github.com/verlet-robotics/verlet-cli.git
cd verlet-cli
pip install -e .
Quick Start
# Authenticate — showcase access code, or a platform account
verlet auth login --kind showcase # prompt for your access code
verlet auth login # platform account (device flow)
# Browse the datasets you can access
verlet datasets list
# Inspect one dataset
verlet datasets info <slug>
# Download a whole dataset
verlet datasets download <slug>
Commands
Datasets — both teleoperation and egocentric (ego) — are served through one
unified verlet datasets surface. Showcase access codes see only the datasets
their code is granted; downloads are gated and whole-dataset.
Removed:
verlet ego list/info/downloadwas retired. Useverlet datasets list/info/downloadinstead — ego data is now addressed by dataset slug, not by internal segment ID.
Authentication
verlet auth login --kind showcase # showcase access code -> short-lived JWT
verlet auth login # platform account (OAuth device flow)
verlet auth logout # remove stored credentials
verlet auth status # show the active credential
Datasets (verlet datasets)
# List the datasets you can access
verlet datasets list
verlet datasets list --task cooking --robot aria # client-side filters
verlet datasets list --json
# Inspect a dataset (showcase codes also see their grants)
verlet datasets info <slug>
# Download a whole dataset
verlet datasets download <slug>
verlet datasets download <slug> -o ./data # custom output directory
verlet datasets download <slug> --variant raw # pick a variant you're granted
verlet datasets download <slug> --scope samples # free-sample subset (showcase)
verlet datasets download <slug> --dry-run # show the plan only
Data Layout
Downloaded data is organized per dataset. Ego datasets land one directory per segment; teleop datasets one directory per episode:
verlet-data/<slug>/
segment_000000/ # ego
rgb.mp4
depth.mkv
pose.parquet
episode_000000/ # teleop
episode_000000.parquet
videos/<camera>.mp4
meta/
Metadata
Release files for verlet 0.16.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| verlet-0.16.1.tar.gz | 206.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| verlet-0.16.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 336.2 kB
Release files / verlet-0.16.1.tar.gz
| Download URL | verlet-0.16.1.tar.gz |
|---|---|
| Size | 206.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0ee99a5a637c90f7cc15a23c86289c26c9f728453f2a30d3bef05f17d70d192d
|
|
BLAKE2b-256 checksum How to use checksums |
5154c747483dc2c3da4edc955f830f5252f81307a6435891d7f1244e42bde4cf
|
| 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 16, 2026.
Transparency logRelease files / verlet-0.16.1-py3-none-any.whl
| Download URL | verlet-0.16.1-py3-none-any.whl |
|---|---|
| Size | 129.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c7f0a1edf712bf0257f94dd256175cbfa5b261fd6de726505c0f752b8edc171e
|
|
BLAKE2b-256 checksum How to use checksums |
bf95016da541cbe0c2e2694577ab7a82c2f537d186e8c9998da3a0074c967ebb
|
| 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 16, 2026.
Transparency log