Start Pod
start_podStart a stopped GPU cloud pod, preview its state and hourly price, then confirm to resume billing; optionally choose same-node, any-node, or waiting placement.
Instructions
Start a stopped pod; hourly billing resumes. With confirm=false (default) it only returns the pod's current
state and hourly price and changes nothing; call again with confirm=true after the user agreed to pay again.
placement: omit it (default) and the server picks what the console's Start button would; the result's
placement says which one it used. Or choose: "same_node" starts it on its original machine now;
"wait_same_node" waits until that machine has room and then starts it there; "any_node" moves it to another
machine now; "wait_any_node" waits until any machine has room and starts it there. A waiting pod shows as
waiting in the pods tool.
any_node and wait_any_node can move the pod: unpreserved workspace files are then permanently deleted and
attached local storage stays on the old machine. For those two, set allow_data_loss=true only after separate
explicit consent to that permanent loss for this pod and placement. allow_data_loss is only sent with an
explicit placement: when the server's own pick would move a pod with unpreserved files, the call fails with
data_loss_consent_required and names that placement. Asynchronous — poll pods for running.
Every write requires operation_id. Reuse the ID returned by the preview, or generate a UUID before the first call. Keep it for confirmation and all retries; a new ID means a new operation. After a timeout, check operation_status and resource state before retrying.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pod | Yes | ||
| confirm | No | ||
| placement | No | ||
| workspace | No | ||
| operation_id | No | ||
| allow_data_loss | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||