Skip to main content

sixtytwo

sixtytwo-cli is the command-line client for sixtytwo, built for the terminal and for coding agents. It covers two jobs:

  • Rent reliability-backed GPUs. sixtytwo rent reserves GPUs that sixtytwo has already qualified, watches them while you run, and refunds the unused time if hardware goes bad.
  • Qualify and monitor your own clusters. sixtytwo runs hardware checks, NCCL benchmarks, straggler detection, and live fault monitoring on GPUs you already have, on both NVIDIA and AMD hardware, and keeps a per-node trust score from every test, fault, and recovery.

sixtytwo rent stays light (no torch), so it runs anywhere. The qualification and monitoring commands pull in the GPU stack only when you ask for it.

Quick start

pip install sixtytwo-cli

# Rent a qualified GPU
sixtytwo rent login                    # paste a token from sixtytwo.ai/account
sixtytwo rent catalog
sixtytwo rent A100_SXM --exec "nvidia-smi -L"  # bounded first test; auto-settles
sixtytwo rent H100_SXM -n 1 -H 2              # 1x H100 for 2 hours

# Or check the GPUs you already have
sixtytwo init
sixtytwo doctor

Install

Requirements: the published slim CLI declares Python 3.9 or newer on macOS (Apple silicon), Linux x86_64/aarch64, and Windows. Python 3.11 or newer is recommended for source development and server workflows.

Optional extras:

pip install 'sixtytwo-cli[gpu]'        # nvidia-ml-py + torch for local GPU checks
pip install 'sixtytwo-cli[skypilot]'   # SkyPilot cloud adapter (see below)
pip install 'sixtytwo-cli[server]'     # local dashboard + collector daemon

Rent GPUs

sixtytwo rent catalog                  # list SKUs and prices
sixtytwo rent H100_SXM -n 8 -H 4       # reserve 8x H100 for 4 hours, wait for READY
sixtytwo rent ls                       # list my reservations
sixtytwo rent status <reservation-id>
sixtytwo rent ssh <reservation-id>     # open a shell on a READY reservation

Every node is validated before you get it and monitored while you use it. Add --region us|eu|asia to pin a geography; billing follows actual usage. The storefront at sixtytwo.ai covers the same flow in the browser.

Team-funded research

Team admins can fund one shared wallet at sixtytwo.ai/team, bulk-invite researchers, and assign a one-time compute budget to each private workspace. Allocations never refresh automatically, and researchers can see only their own workspace and rentals.

sixtytwo rent teams                     # list teams available to this token
sixtytwo rent team-use <org-id>         # save the private team workspace
sixtytwo rent credits                   # show allocation and current availability
sixtytwo rent H100_SXM --exec "nvidia-smi -L"

Use --team <org-id> on rent, credits, or topup to override the saved team for one command. Team top-ups require an org admin.

Qualify and monitor your own GPUs

These commands read a sixtytwo.yaml, so run init once first. It detects this machine (and your scheduler, if any) and writes the config into the current directory; everything below loads it.

sixtytwo init                          # writes ./sixtytwo.yaml (run this first)
sixtytwo doctor                        # validate this box: drivers, GPUs, topology
sixtytwo doctor --all-nodes --json     # validate every node in the cluster
sixtytwo test --quick --all            # fast per-node qualification
sixtytwo test --full gpu-01,gpu-02     # full suite, including NCCL
sixtytwo security --all                 # separate report-only security posture
sixtytwo launch --pre-check python train.py   # qualify, then run with live monitoring
sixtytwo nodes                         # trust scores and fault history

doctor --all-nodes reports each node's GPU inventory, not just the local host's. Results land in a local trust registry, so a node's history (tests, faults, recoveries) follows it over time.

Straggler detection runs at both stages. test --full flags a GPU that is slower than its node peers (an identical kernel timed per GPU) or below its model's reference baseline, before you commit a run to it. During a run, launch watches per-rank step times and flags a rank that falls behind the others, so a GPU that degrades into a straggler mid-job is caught too.

Slurm clusters

Run init on the login node (or inside an allocation). It detects Slurm, fills the node list from sinfo/scontrol, and sets remote.mode: slurm, so test and doctor --all-nodes dispatch each node's checks through srun. Confirm the GPU partition and per-node GPU count in sixtytwo.yaml (the per-node count can't be detected from a GPU-less login node):

cluster:
  slurm:
    partition: gpu        # your GPU partition
    gpus_per_node: 8

On a large or multi-partition cluster init lists every node it can see, so trim cluster.nodes to the GPU nodes you actually want to qualify before running doctor --all-nodes or test --all.

SSH clusters (no scheduler)

Any set of boxes you can ssh into can be treated as a cluster: set remote.mode: ssh and list the nodes, where entries accept user@host:port so cloud pods with one public port per node (RunPod, Vast) work directly:

cluster:
  nodes:
    - root@203.0.113.7:45663
    - root@203.0.113.9:11542
remote:
  mode: ssh
  ssh_key_path: ~/.ssh/id_ed25519

doctor --all-nodes and test --all --parallel 8 then drive every node over ssh.

Kubernetes clusters (qualification and distributed PyTorch)

On a GPU Kubernetes cluster, start with a qualification audit. It checks the capabilities that matter for large training jobs: node and GPU readiness, the GPU Operator and RuntimeClass, RDMA/Network Operator, CNI, default and ReadWriteMany storage, LoadBalancer support, node-problem-detector, the monitoring stack, distributed-training and queue-scheduling APIs, and the RBAC needed to run and observe workloads:

sixtytwo k8s qualify --nodes 4 --gpus-per-node 8 --gpu-type H100_SXM \
  --output qualification.json

The default run is read-only and writes one machine-readable evidence report with a remediation per failing check. --full adds two functional probes: a cross-node ReadWriteMany write/read test and the multi-node collective test below. Checks that need a representative workload, such as training MFU and disaggregated-inference throughput, are reported as explicit not_run findings rather than being inferred from synthetic probes.

For the fabric itself, run a real multi-node torch.distributed test, a collective-bandwidth sweep plus a few DDP training steps, across nodes:

sixtytwo k8s dist --nodes 2 --gpus-per-node 8 --gpu-type H100_SXM

It launches one pod per node as a Kubernetes Indexed Job, with ranks coordinated by torch's c10d rendezvous over a headless Service, so there is no Kubeflow or MPI operator to install and no SSH between pods. The result is scored against the same NCCL thresholds as the rest of the suite. Add --dry-run to print the manifests without touching the cluster, --json for the full report, or --no-cleanup to leave the Job up for inspection. The machine you run it from needs only kubectl access; torch runs in the pods. sixtytwo k8s-dist still works as an alias of k8s dist.

Prerequisites: Kubernetes 1.24+, the NVIDIA device plugin and the nvidia RuntimeClass (the usual GPU-pod setup), at least two GPU nodes, and a sixtytwo namespace with a sixtytwo-agent service account:

kubectl create namespace sixtytwo
kubectl create serviceaccount sixtytwo-agent -n sixtytwo

SkyPilot

There are two ways to combine sixtytwo with SkyPilot:

# 1. Qualify a cluster you launched on any cloud SkyPilot supports
sixtytwo skypilot qualify my-cluster --mode quick

# 2. Provision sixtytwo's own GPUs through SkyPilot with `cloud: sixtytwo`
pip install 'sixtytwo-cli[skypilot]'
sixtytwo skypilot install              # register sixtytwo as a SkyPilot cloud
sky show-gpus --cloud sixtytwo

sixtytwo skypilot install is opt-in: it wires the adapter into the active virtualenv so sky launch can reserve reliability-backed GPUs with cloud: sixtytwo. Run sixtytwo skypilot --help for the full set of subcommands.

Topology and fabric health

The full test suite maps how a node is actually wired and checks the fabric it sits on:

  • GPU topology: the NVLink and XGMI link matrix on every node, with PCIe-only or mixed-link wiring flagged before it slows a collective.
  • InfiniBand fabric: the fabric is mapped to show which leaf switch each node hangs off (one sweep per cluster, reused across nodes), and port counters are classified so congestion reads as congestion rather than a cable fault.
  • GPU to NIC affinity: an NCCL probe across all GPUs verifies rail-optimized placement.
  • Diagnosis with opt-in repairs: failures map to a remediation plan (restart fabric manager, reset wedged GPUs, fix clock sync). Everything is off by default and dry-run first; fixes only execute when recovery.in_place_fixes.enabled is set, stop at the first verified repair, and never escalate to a disruptive action without a fresh diagnosis.

Hosted dashboards

Stream telemetry to sixtytwo.ai and watch the fleet from a browser:

sixtytwo connect --source ssh --name my-cluster   # register (token from the account page)
sixtytwo monitor                                  # stream per-GPU telemetry
sixtytwo install-agent                            # or install as a systemd service

The cluster page shows live per-node tiles, a node x GPU utilization heat map, and a 24h history; on Slurm clusters the agent also attributes GPU hours to users and accounts, feeding a chargeback report that exports to CSV.

Metrics for Grafana

sixtytwo metrics serve exposes a Prometheus /metrics endpoint backed by the local trust registry: trust scores, fault counters, recovery downtime, and per-check status. sixtytwo metrics export-grafana prints a curated dashboard you can import as is.

sixtytwo metrics serve --host 0.0.0.0 --port 9620
sixtytwo metrics export-grafana --output sixtytwo-overview.json

License

Commercial. The bundled LICENSE governs use. Learn more at sixtytwo.ai.

Metadata

Release files for sixtytwo-cli 0.4.0

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

Built distributions (wheels)

Table of built distributions (wheels) for sixtytwo-cli 0.4.0
File Actions
sixtytwo_cli-0.4.0-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details for sixtytwo_cli-0.4.0-cp314-cp314-win_amd64.whl
sixtytwo_cli-0.4.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for sixtytwo_cli-0.4.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
sixtytwo_cli-0.4.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details for sixtytwo_cli-0.4.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
sixtytwo_cli-0.4.0-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details for sixtytwo_cli-0.4.0-cp314-cp314-macosx_11_0_arm64.whl
sixtytwo_cli-0.4.0-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for sixtytwo_cli-0.4.0-cp313-cp313-win_amd64.whl
sixtytwo_cli-0.4.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for sixtytwo_cli-0.4.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
sixtytwo_cli-0.4.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.28+ ARM64, Linux glibc 2.17+ ARM64 Details for sixtytwo_cli-0.4.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
sixtytwo_cli-0.4.0-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details for sixtytwo_cli-0.4.0-cp313-cp313-macosx_11_0_arm64.whl
sixtytwo_cli-0.4.0-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for sixtytwo_cli-0.4.0-cp312-cp312-win_amd64.whl
sixtytwo_cli-0.4.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for sixtytwo_cli-0.4.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
sixtytwo_cli-0.4.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ ARM64, Linux glibc 2.17+ ARM64 Details for sixtytwo_cli-0.4.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
sixtytwo_cli-0.4.0-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details for sixtytwo_cli-0.4.0-cp312-cp312-macosx_11_0_arm64.whl
sixtytwo_cli-0.4.0-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for sixtytwo_cli-0.4.0-cp311-cp311-win_amd64.whl
sixtytwo_cli-0.4.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for sixtytwo_cli-0.4.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
sixtytwo_cli-0.4.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ ARM64, Linux glibc 2.17+ ARM64 Details for sixtytwo_cli-0.4.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
sixtytwo_cli-0.4.0-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details for sixtytwo_cli-0.4.0-cp311-cp311-macosx_11_0_arm64.whl
sixtytwo_cli-0.4.0-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for sixtytwo_cli-0.4.0-cp310-cp310-win_amd64.whl
sixtytwo_cli-0.4.0-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for sixtytwo_cli-0.4.0-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
sixtytwo_cli-0.4.0-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ ARM64, Linux glibc 2.17+ ARM64 Details for sixtytwo_cli-0.4.0-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
sixtytwo_cli-0.4.0-cp310-cp310-macosx_11_0_arm64.whl CPython 3.10 CPython 3.10 macOS 11.0+ ARM64 Details for sixtytwo_cli-0.4.0-cp310-cp310-macosx_11_0_arm64.whl
sixtytwo_cli-0.4.0-cp39-cp39-win_amd64.whl CPython 3.9 CPython 3.9 Windows x86-64 Details for sixtytwo_cli-0.4.0-cp39-cp39-win_amd64.whl
sixtytwo_cli-0.4.0-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.9 CPython 3.9 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for sixtytwo_cli-0.4.0-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
sixtytwo_cli-0.4.0-cp39-cp39-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.9 CPython 3.9 Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details for sixtytwo_cli-0.4.0-cp39-cp39-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
sixtytwo_cli-0.4.0-cp39-cp39-macosx_11_0_arm64.whl CPython 3.9 CPython 3.9 macOS 11.0+ ARM64 Details for sixtytwo_cli-0.4.0-cp39-cp39-macosx_11_0_arm64.whl

Total release size: 219.4 MB

Release files / sixtytwo_cli-0.4.0-cp314-cp314-win_amd64.whl

Download URL sixtytwo_cli-0.4.0-cp314-cp314-win_amd64.whl
Size 7.6 MB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
2cf3159dff9c2284fa3719810f50dcc0a8fe11349ed568777e27dc165c0b1516
BLAKE2b-256 checksum
How to use checksums
06a780cd8961c6691355ef36c6fc84c1b78b8e0dab78910c434794f1f92bc1b9
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL sixtytwo_cli-0.4.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 10.4 MB
Tags CPython 3.14 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
a805246e5bf98ab8b6401e9a7d25cbc35d4d89c6fcf1544e6cc9d6348bf423ab
BLAKE2b-256 checksum
How to use checksums
d98f1c03a154b53a3ac86a719ff7f6b2d9c20931da6f28675671f181155dd991
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL sixtytwo_cli-0.4.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 9.6 MB
Tags CPython 3.14 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
3bd986388c1428ba49d73ae4dd3d8f567a869a600d0fe4ca8910a4f5dd8a35e9
BLAKE2b-256 checksum
How to use checksums
6685c9e5a15d84a7e10ada86caa6d193bf9381702f8d9ba10f52fa7d8db29d57
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp314-cp314-macosx_11_0_arm64.whl

Download URL sixtytwo_cli-0.4.0-cp314-cp314-macosx_11_0_arm64.whl
Size 8.5 MB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
c4063a3a9e52fdd56a8fa5b127262404e8e3190df10ebbe8bf3a64b3cf5fb39b
BLAKE2b-256 checksum
How to use checksums
577acf0d1bf1dcec54878da7a4afb3fd44dc0830b11c5902fac0afcaf1ba82dc
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp313-cp313-win_amd64.whl

Download URL sixtytwo_cli-0.4.0-cp313-cp313-win_amd64.whl
Size 7.4 MB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
1156327d502a82c96395600339f496eadd82b676ef509b685a88752b8917ddbf
BLAKE2b-256 checksum
How to use checksums
1b15728742ffb0bfacf784a5f465cfb21be9031fa69f1d938f996f7c4dd170c3
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL sixtytwo_cli-0.4.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 10.3 MB
Tags CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
befa5d79230f3e83ddf3b146b18f3ce53aba51f9df2081869ab6ce9a555cc980
BLAKE2b-256 checksum
How to use checksums
69197dd7de1893ae6686dfd94425da67e36db42e361fcb83608f55b1a04bb0be
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL sixtytwo_cli-0.4.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 9.4 MB
Tags CPython 3.13 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
eec66f39dc3c1c6c88683617c9a4123e481aae0acd762e2c70514de561b3f5bd
BLAKE2b-256 checksum
How to use checksums
024870c17460e7f33f7f9deed69dfbc862fbd9ca4066193609970933a7bbc216
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp313-cp313-macosx_11_0_arm64.whl

Download URL sixtytwo_cli-0.4.0-cp313-cp313-macosx_11_0_arm64.whl
Size 8.5 MB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
83a0603f5e615ddb41f7574a7a0f41951b5e0397bc76522b246514de0dba25dd
BLAKE2b-256 checksum
How to use checksums
a7f78329fec1c8dbccf6ca61b83ce44730e484c80ac136f095f1fbecf7b64975
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp312-cp312-win_amd64.whl

Download URL sixtytwo_cli-0.4.0-cp312-cp312-win_amd64.whl
Size 7.4 MB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
575828e438d16adf417df5fceba4f772b87fd07cc8a044d53a6cbdc5b5a9e73b
BLAKE2b-256 checksum
How to use checksums
d475846bf9362ebc562e26c879af59b5f6b9886ea5df1deed0a94f4b4f7981ae
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL sixtytwo_cli-0.4.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 10.3 MB
Tags CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
6a64d79b5733cc72704e7448d35736f3d607a610672b1a078f4cb8aba67719a6
BLAKE2b-256 checksum
How to use checksums
6502e87d5bf2d0f24ad918e1c04699b70201583ee582da67bba814ef0d28ab4c
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL sixtytwo_cli-0.4.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 9.4 MB
Tags CPython 3.12 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
d0fffa358da5201b73ad6f93d585d0497d0a6efed2442e3fb4e127f66f56f83d
BLAKE2b-256 checksum
How to use checksums
d287996069c19985a9418410f76aa8b6a63bc8432e186010d97ebe7eb165db63
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp312-cp312-macosx_11_0_arm64.whl

Download URL sixtytwo_cli-0.4.0-cp312-cp312-macosx_11_0_arm64.whl
Size 8.5 MB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
8b1222c952c4a4630280dc9205cb811e49be54aa9cd697c51f6ad7bb9ca9d227
BLAKE2b-256 checksum
How to use checksums
c3c4e04b63bac8a96ee7d257d9671091ec2f0be47da8827ecad102de2081d420
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp311-cp311-win_amd64.whl

Download URL sixtytwo_cli-0.4.0-cp311-cp311-win_amd64.whl
Size 7.7 MB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
8a4048f303a3a2cb335bbe655957cc9a68252df9e1d0d738c9f5a8f1e3040860
BLAKE2b-256 checksum
How to use checksums
029dcb118c278ac66bea70dd09c2f5e164214d7233ba69a4c66ac730a61ffa6e
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL sixtytwo_cli-0.4.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 10.9 MB
Tags CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
93a27acbf762a1c52ca2375adfd4752e9b9833e9c122b0e580b9847180ffbf37
BLAKE2b-256 checksum
How to use checksums
760a2ffb7f5cfc004652e67032d357840c8073c1608c97b456986baedc9a61bf
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL sixtytwo_cli-0.4.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 10.1 MB
Tags CPython 3.11 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
ffa27534633e46e1e864b4314b498d4e20896be5bfaf6b4f517add84e79c2a98
BLAKE2b-256 checksum
How to use checksums
6d22574a2d6d496971ba96efd2e4ca81f8cae1f045b1a6e220bbf6fe05e0b5ec
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp311-cp311-macosx_11_0_arm64.whl

Download URL sixtytwo_cli-0.4.0-cp311-cp311-macosx_11_0_arm64.whl
Size 8.6 MB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
3d075bbd9a5c87403a0733d2a7c418fd721f8d6d519c2966347df289ade95e42
BLAKE2b-256 checksum
How to use checksums
6a699704b915ff9bd6b53181aee054d8173df22422722904f8494613493ee2cf
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp310-cp310-win_amd64.whl

Download URL sixtytwo_cli-0.4.0-cp310-cp310-win_amd64.whl
Size 7.6 MB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
193fefa60be83f3dc71d1a02f8f3a9b7845dc770fcc967d26751f5ed468f5b09
BLAKE2b-256 checksum
How to use checksums
285c9e22059dbaad2f47e3eded13d82cb0b2d8eee1c0ecf6b0089e89977359ef
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL sixtytwo_cli-0.4.0-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 11.0 MB
Tags CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
e3f76632a15fcaf62dd276e2edfe0481a6e329fd4c344b3fe2a0d890f5edadef
BLAKE2b-256 checksum
How to use checksums
9eb72179acb78d51055c7fb13a1f7809f15acc3d26bef4403a93c33bcbb379d6
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL sixtytwo_cli-0.4.0-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 10.1 MB
Tags CPython 3.10 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
3e3da18e7534330d1e665cd4bce22d5c7a0d1240538dc0b40d96b1e213a5c817
BLAKE2b-256 checksum
How to use checksums
56d382edc55ab820448094df8120717051ef48e2e2dbb67010a17d29a8b817d1
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp310-cp310-macosx_11_0_arm64.whl

Download URL sixtytwo_cli-0.4.0-cp310-cp310-macosx_11_0_arm64.whl
Size 8.7 MB
Tags CPython 3.10 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
fff9751a19f9a5f143a45f46da8dd2f799bc664333b6cf67ed709ecc59e74c29
BLAKE2b-256 checksum
How to use checksums
1034c47bfba31cffa35d10d593781229561269b7300abaef1eabf34c8cc6a13d
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp39-cp39-win_amd64.whl

Download URL sixtytwo_cli-0.4.0-cp39-cp39-win_amd64.whl
Size 7.7 MB
Tags CPython 3.9 Windows x86-64
SHA-256 checksum
How to use checksums
a73d85e2bc36dc6a1436ca47eea87d71b438344f3ba8a924674a0e96d0345de7
BLAKE2b-256 checksum
How to use checksums
cdd4096fdbf18f410d0aeb48745833bbf84d0a76c5d10b71d736775e86aad14e
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL sixtytwo_cli-0.4.0-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 11.0 MB
Tags CPython 3.9 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
f3bc313b76d40fde8cddd2416595d502d4a7136716d854b22e31b4b17a5ff7ef
BLAKE2b-256 checksum
How to use checksums
8a2695c203733a7bb39099f89c8f1a3d1f20b7f74df0f9ea8db714e61c859522
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp39-cp39-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL sixtytwo_cli-0.4.0-cp39-cp39-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 10.2 MB
Tags CPython 3.9 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
6699bb916bc3de77c5b1217ecfb7acbd7daae2c1a54b2a1229260f47e447dec1
BLAKE2b-256 checksum
How to use checksums
08022f04c295225f96a461481741e1f4f5978e8df237eb31708465f7544df57f
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 Aug 20, 2026.

Transparency log

Release files / sixtytwo_cli-0.4.0-cp39-cp39-macosx_11_0_arm64.whl

Download URL sixtytwo_cli-0.4.0-cp39-cp39-macosx_11_0_arm64.whl
Size 8.7 MB
Tags CPython 3.9 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
2c7099ee4f07313979ee18955005707a0955ba369e494fa88e29041b15ff7e93
BLAKE2b-256 checksum
How to use checksums
4ae5a186fb9472f1289753d6838b49c7c722daa6ddae395cea2d7a7c4fbd781d
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 Aug 20, 2026.

Transparency log

Security for sixtytwo-cli 0.4.0

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 24 files in this release have been uploaded with provenance metadata.

Select from 24 files

Attestation for sixtytwo_cli-0.4.0-cp314-cp314-win_amd64.whl

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 Aug 20, 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.

Release history Release notifications | RSS feed

This release

0.4.0 This release

24 release files Full provenance

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