Get a VM with its GPU/node/template info and price

compute-fabric capability tier (e.g. "pod"); empty for a plain VM

compute-fabric compute class (interruptible|reserved); empty for a plain VM

This VM's usage is recorded but never charged: a provider org consuming GPUs on a node it owns under its own reservation. pricePerHourCents still reports the real rate (the measurement is kept, the charge is waived) so a client showing a rate MUST also show this or it will display a bill that never arrives.

bundled hourly rate. When the VM has an open usage session this is the rate LOCKED at session open (what settlement charges); otherwise the rate a session WOULD lock: the fabric admission snapshot for a pod, else the current catalog rate for the VM's shape.

true = open endpoint (no data-plane auth); false = require an org API key

managed-service tag; empty for a plain VM

ready-to-paste ssh command (ssh <handle>@<host>)

RunPod-style SSH handle (first label of endpointUrl); used as the SSH username

data-plane SSH gateway host, e.g. ssh.run.beta.openrelay.inc

true when SSH should work now. Observed: a node-side probe saw the guest sshd answer. Falls back to the running-status guess on nodes not yet reporting probes (sshState=unverified).

why sshReady is what it is. booting = the VM is running but its guest OS has not started sshd yet (GPU VMs take minutes); unverified = no probe signal for this node, sshReady is a guess; offline = the VM is not running.

human-readable explanation of sshState, safe to show to the customer

login user the gateway lands as inside the VM (e.g. ubuntu)

human-readable cause for failed/stuck states

RFC3339 time the VM was terminated. Set only once status is "terminated" (a stopped/failed VM can restart, so it has none); absent while the VM is live. On a terminated VM, healthy is false and provisioningStage is absent.