Run a deployment longer
extend_deploymentAdd hours to the term of a deployment that is requested, queued, provisioning or running. Same machine, same SSH details; billing stays per minute. Tell the user the extra cost (hours × gpu_count × rate) and get a yes first. Retry-safe: see idempotency_key.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"id": "<id>",
"hours": "<hours>",
"confirm": "<confirm>"
},
"name": "extend_deployment"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The deployment id (rnt_… on a live key, snd_… in the sandbox). | |
| hours | Yes | Hours to add. The new end may not be more than 720 hours away. | |
| confirm | Yes | Must be true. It states that the user approved this exact action after seeing what it does and costs. With a sandbox key (tml_test_…) nothing is real and it may be set freely. | |
| idempotency_key | No | Optional. 8 to 128 characters. Reuse the same value when retrying the same request. Left out, one is derived from the request and the UTC date, so the identical request the same day returns the first answer; pass a new value to really do it a second time. |