Visor The `hanzo visor` commands.
Also for this capability: API · CLI · MCP · SDKs
The compute you rent from Hanzo: machines, GPUs and clusters — launch one, resize it, tear it down.
API reference →
hanzo visor 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 visor clusters createAttaches a BYO cluster to the caller's org — the kubeconfig is validated, KMS-sealed and added to the fleet — and… hanzo visor clusters listReturns the caller org's clusters from both sources: the managed clusters projected from Visor's node pools, and the… hanzo visor clusters pools create <clusterId>Adds a node pool to one of the caller org's clusters and answers 201 with the created pool. hanzo visor clusters pools rm <clusterId> <poolId>Removes a node pool from one of the caller org's clusters. hanzo visor clusters pools scale <clusterId> <poolId>Resizes a node pool to an absolute node count and returns the pool as Visor reports it after the change. hanzo visor clusters rm <id>Removes a BYO cluster from the caller org's fleet.
Command What it does hanzo visor compute bots get <id>Returns one of the caller org's bot machines with its agent binding. hanzo visor compute bots id add <id> <action>Message a bot, or stop it, by naming the action in the path hanzo visor compute bots launchLaunch a bot machine — an agent plus the machine that runs it — or price one hanzo visor compute bots listReturns the caller org's bot machines — the kind=bot machines — each joined with the agent binding that says which… hanzo visor compute bots rm <id>Tears down both halves of a bot: it unbinds the agent (best-effort — a bot with no binding still deletes), then… hanzo visor compute regionsRegions lists the regions a machine can be launched in. hanzo visor compute sizesSizes lists the machine sizes available to launch, with their specifications.
Command What it does hanzo visor fleet getReturns every compute unit the caller's org has, from every source, each carrying its latest utilization: agent… hanzo visor fleet jobs cancel <id>Cancels a queued or running render in the caller's org. hanzo visor fleet jobs listReturns the caller org's gpu-jobs render queue, each row tagged with the GPU it targets (empty = the shared any-GPU… hanzo visor fleet samples createRecords a BYO worker's live GPU utilization into the SAME series the fleet board overlays. hanzo visor fleet samples getReturns the caller org's utilization series, oldest first. hanzo visor fleet workersReturns the caller org's BYO machines — the ones that dialed in via hanzo link — with everything each host reported…
Command What it does hanzo visor gpus alertsIs an HONEST empty surface: Visor exposes no GPU alert inventory, so this returns [] rather than fabricating alerts. hanzo visor gpus getReturns one row per physical accelerator the caller's org has, derived from its real GPU machines (the size slug says…
Command What it does hanzo visor k8s clusters createProvisions a DOKS cluster for the caller's org and answers 201. hanzo visor k8s clusters get <id>Returns one cluster's detail: node pools + worker nodes. hanzo visor k8s clusters listLists the org's DOKS clusters (Visor, house account) folded with the org's BYO clusters — ONE fleet cluster view under… hanzo visor k8s clusters rm <id>Destroys a DOKS cluster by id and answers 204. hanzo visor k8s nodesReturns every DOKS worker node in the org's clusters as a machine — the SAME set the fleet folds in (managedMachines),…
Command What it does hanzo visor machines agent clear <id>Detaches the agent runtime from one of the caller org's machines. hanzo visor machines agent get <id>Returns the agent binding of one of the caller org's machines, or 404 when the machine runs no bot runtime. hanzo visor machines agent replace <id>Binds a cloud Agent to one of the caller org's machines: the machine is recorded as running that Agent's @hanzo/bot… hanzo visor machines agentsReturns every agent↔machine binding in the caller's org — which machines are running which cloud Agent, with vm's own… hanzo visor machines createLaunch a metered machine for your org, or price one first with dryRun hanzo visor machines get <id>Returns one of the caller org's machines by its org-scoped name. hanzo visor machines listReturns every machine the caller's org has — Visor's registry, the live DigitalOcean droplets and the DOKS worker nodes… hanzo visor machines rm <id>Terminates one of the caller org's machines.
How is this guide?