# Compute URL: https://docs.hanzo.ai/docs/cli/compute > The `hanzo compute` commands. Also for this capability: [API](https://docs.hanzo.ai/docs/openapi/compute) · **CLI** · [MCP](https://docs.hanzo.ai/docs/mcp-tools/compute) · [SDKs](https://docs.hanzo.ai/docs/sdks) The compute you rent from Hanzo: machines, GPUs and clusters — launch one, resize it, tear it down. [API reference →](https://docs.hanzo.ai/docs/openapi/compute) ```bash hanzo compute clusters list ``` Every command takes `--json` for the raw response and `--help` for its own flags. Sign in once with `hanzo auth login`; the commands below use that session, and the org they act in is the one it carries. | Command | What it does | | ----------------------- | ----------------------------------------------------------------------- | | `hanzo compute regions` | Lists the regions a machine can be launched in. | | `hanzo compute sizes` | Lists the machine sizes available to launch, with their specifications. | ### Clusters | Command | What it does | | --------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `hanzo compute clusters create` | Attaches a BYO cluster to the caller's org — the kubeconfig is validated, KMS-sealed and added to the fleet — and answers 201 with the cluster as it now appears on GET /v1/compute/clusters. | | `hanzo compute clusters list` | Returns the caller org's clusters from both sources: the managed clusters projected from Visor's node pools, and the BYO clusters attached to the caller's project. | | `hanzo compute clusters pools create ` | Adds a node pool to one of the caller org's clusters and answers 201 with the created pool. | | `hanzo compute clusters pools rm ` | Removes a node pool from one of the caller org's clusters. | | `hanzo compute clusters pools scale ` | Resizes a node pool to an absolute node count and returns the pool as Visor reports it after the change. | | `hanzo compute clusters rm ` | Removes a BYO cluster from the caller org's fleet. | ### Fleet | Command | What it does | | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `hanzo compute fleet get` | Returns every compute unit the caller's org has, from every source, each carrying its latest utilization: agent run-targets, the BYO machines that dialed in, attached BYO clusters and Visor-provisioned machines. | | `hanzo compute fleet jobs cancel ` | Cancels a queued or running render in the caller's org. | | `hanzo compute fleet jobs list` | Returns the caller org's gpu-jobs render queue, each row tagged with the GPU it targets (empty = the shared any-GPU lane) and the node claiming it, optionally narrowed to one GPU's queue and/or one status. | | `hanzo compute fleet samples create` | Records a BYO worker's live GPU utilization into the SAME series the fleet board overlays. | | `hanzo compute fleet samples get` | Returns the caller org's utilization series, oldest first. | | `hanzo compute fleet workers` | Returns the caller org's BYO machines — the ones that dialed in via `hanzo link` — with everything each host reported about itself. | ### GPUs | Command | What it does | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `hanzo compute gpus alerts` | An HONEST empty surface: Visor exposes no GPU alert inventory, so this returns \[] rather than fabricating alerts. | | `hanzo compute gpus get` | Returns one row per physical accelerator the caller's org has, derived from its real GPU machines (the size slug says how many cards a node holds) and from the accelerators BYO workers report through nvidia-smi. | ### K8s | Command | What it does | | ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | `hanzo compute k8s clusters create` | Provisions a DOKS cluster for the caller's org and answers 201. | | `hanzo compute k8s clusters get ` | Returns one cluster's detail: node pools + worker nodes. | | `hanzo compute k8s clusters list` | Lists the org's DOKS clusters (Visor, house account) folded with the org's BYO clusters — ONE fleet cluster view under the unified k8s noun. | | `hanzo compute k8s clusters rm ` | Destroys a DOKS cluster by id and answers 204. | | `hanzo compute k8s nodes` | Returns every DOKS worker node in the org's clusters as a machine — the SAME set the fleet folds in (managedMachines), exposed directly under the k8s noun. | ### Machines | Command | What it does | | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `hanzo compute machines agent clear ` | Detaches the agent runtime from one of the caller org's machines. | | `hanzo compute machines agent get ` | Returns the agent binding of one of the caller org's machines, or 404 when the machine runs no bot runtime. | | `hanzo compute machines agent replace ` | Binds a cloud Agent to one of the caller org's machines: the machine is recorded as running that Agent's @hanzo/bot runtime. | | `hanzo compute machines agents` | Returns every agent↔machine binding in the caller's org — which machines are running which cloud Agent, with vm's own reconciled status. | | `hanzo compute machines create` | Launch a metered machine for your org, or price one first with dryRun | | `hanzo compute machines get ` | Returns one of the caller org's machines by its org-scoped name. | | `hanzo compute machines id add ` | Message a bot, or stop it, by naming the action in the path | | `hanzo compute machines list` | Returns every machine the caller's org has — Visor's registry, the live DigitalOcean droplets and the DOKS worker nodes (deduped into one union), plus the BYO machines that dialed in via `hanzo link` (provider "byo"). | | `hanzo compute machines rm ` | Terminates one of the caller org's machines. |