From f99763660b3a50af5871a6879da4d030a2121d80 Mon Sep 17 00:00:00 2001 From: Aleksey Proshutinskiy Date: Fri, 13 Nov 2026 21:31:52 +0200 Subject: [PATCH 1/2] docs: state the legacy GPU API deprecation in the agreed wording --- docs/build/api/gpu_cloud.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/build/api/gpu_cloud.md b/docs/build/api/gpu_cloud.md index c9e84f4..2f91cf6 100644 --- a/docs/build/api/gpu_cloud.md +++ b/docs/build/api/gpu_cloud.md @@ -309,7 +309,7 @@ Lists take `page` and `perPage` (up to 200, 50 by default) and return `items` an ## Legacy GPU API :::warning -The legacy GPU API is deprecated. Use `/v3/gpu` for new integrations, and move existing integrations to it. +The legacy GPU API (`/gpu`) is deprecated. It keeps working and gets no new features; use `/v3/gpu`. No shutdown date is set. ::: The earlier GPU API under `https://api.fluence.dev/gpu/...` still works for existing integrations, and its paths and responses do not change. New instances rented through the legacy API are billed the same way as `/v3/gpu` instances: by the billing step and minimum of their offer. From 246bd7764c45f7795d4065b840c92c8feb76a67b Mon Sep 17 00:00:00 2001 From: Aleksey Proshutinskiy Date: Fri, 13 Nov 2026 21:35:24 +0200 Subject: [PATCH 2/2] docs: state when GPU billing runs in the agreed wording --- docs/build/gpu_cloud/overview.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/build/gpu_cloud/overview.md b/docs/build/gpu_cloud/overview.md index e4785f5..2e671f2 100644 --- a/docs/build/gpu_cloud/overview.md +++ b/docs/build/gpu_cloud/overview.md @@ -64,10 +64,9 @@ Use spot instances for work that can stop and start again, and keep your data ou GPU instances are billed in USD from your account balance, for the time they run. -- Billing starts when the instance becomes `running`. A launch that fails before that is not billed. +- Billing runs from the moment the instance becomes `running` until it ends, also while it is powered off, not ready, or not reporting its state. It stops when you terminate the instance or when it ends for another reason. The status can still read `terminating` for a short while. If the instance lived less than the minimum period, the minimum charge applies. A launch that fails before the instance runs is not billed. - Each offer has a billing step and a minimum period. Most offers bill per minute with a minimum of 20 minutes. Some offers bill per hour with a minimum of 1 hour. The offer and the instance show their terms. - An instance that starts running costs at least the minimum charge: the price for the minimum period. After the minimum period, you pay per billing step. -- Billing stops when you terminate the instance, or when it ends for another reason. The instance can still show `terminating` for a short while. If the instance lived less than the minimum period, the minimum charge applies. - After an instance ends, its total charge can read 0 or grow for a few minutes. It is final when it is above 0 and does not change between two reads a minute apart. To launch an instance, your balance must cover its minimum charge on top of the amount that your running resources already hold.