From 5e055fab40c60052f2e79244c989697b32391c83 Mon Sep 17 00:00:00 2001 From: Aleksey Proshutinskiy Date: Fri, 13 Nov 2026 21:51:08 +0200 Subject: [PATCH 1/2] docs: GPU Cloud is open to every account --- docs/build/gpu_cloud/instance_rent.md | 2 -- docs/build/overview.md | 2 +- docs/build/registration.md | 2 +- 3 files changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/build/gpu_cloud/instance_rent.md b/docs/build/gpu_cloud/instance_rent.md index 3f184c0..541685d 100644 --- a/docs/build/gpu_cloud/instance_rent.md +++ b/docs/build/gpu_cloud/instance_rent.md @@ -6,8 +6,6 @@ description: Rent a GPU container, GPU VM, or bare metal server, on demand or as This guide shows how to rent a GPU instance in the **GPU cloud** section of the Fluence Console. For workload types, spot instances, statuses, and billing, see [GPU Cloud concepts](./overview.md). To rent from code, see the [GPU Cloud API](../api/gpu_cloud.md). -GPU Cloud is not open to every account. If the sidebar has no **GPU cloud** section, or the console shows **GPU Cloud is temporarily unavailable**, your account has no access to GPU Cloud yet. Contact support at support@fluence.ai. - Before you start, top up your balance. To launch, your balance must cover the minimum charge of the instance on top of what your running resources already hold. See the [billing model](./overview.md#billing-model). ## Choose a GPU diff --git a/docs/build/overview.md b/docs/build/overview.md index bc6680c..7f81e93 100644 --- a/docs/build/overview.md +++ b/docs/build/overview.md @@ -33,4 +33,4 @@ The sidebar of the Fluence Console has these sections: ## Pay for compute -A new account can rent CPU compute right after registration. GPU Cloud is not open to every account: if the console shows **GPU Cloud is temporarily unavailable**, contact support. Rent is charged from your prepaid balance in USD, so top it up first. You can top it up by card or in crypto in the console. An AI agent can also top up over HTTP with USDC through [x402](./api/x402.md). See [Payment and balance management](./balance.md). +A new account can rent GPU and CPU compute right after registration. Rent is charged from your prepaid balance in USD, so top it up first. You can top it up by card or in crypto in the console. An AI agent can also top up over HTTP with USDC through [x402](./api/x402.md). See [Payment and balance management](./balance.md). diff --git a/docs/build/registration.md b/docs/build/registration.md index 0a4ebcd..52d5415 100644 --- a/docs/build/registration.md +++ b/docs/build/registration.md @@ -15,7 +15,7 @@ The Fluence Console uses one page to sign in and to create an account. After the first sign-in, the console asks for your name, last name, job role, and company. You can fill them in or click **Skip**. You can change them later in **Settings** > **Account**. -After you register, you can rent CPU compute. GPU Cloud is not open to every account. See [Rent a GPU instance](./gpu_cloud/instance_rent.md). Rent is charged from a balance in USD, so top it up first. See [Payment and balance management](./balance.md). +After you register, you can rent GPU and CPU compute. Rent is charged from a balance in USD, so top it up first. See [Payment and balance management](./balance.md). :::tip An AI agent or a script doesn't need to register. [Paying with x402](./api/x402.md) creates an account for the paying wallet. From 3b22c92fc788fafb47a2e6b5a64a9400d23d342e Mon Sep 17 00:00:00 2001 From: Aleksey Proshutinskiy Date: Fri, 13 Nov 2026 22:07:40 +0200 Subject: [PATCH 2/2] docs: GPU access needs a new API key for older keys --- docs/build/api/gpu_cloud.md | 2 +- docs/build/api/overview.md | 2 +- docs/build/overview.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/build/api/gpu_cloud.md b/docs/build/api/gpu_cloud.md index c9e84f4..1891cf6 100644 --- a/docs/build/api/gpu_cloud.md +++ b/docs/build/api/gpu_cloud.md @@ -21,7 +21,7 @@ Send an API key in the `X-API-KEY` header, or an access token in `Authorization: | List images, read offers, get quotes, and read your instances | `gpu:read` | | Create, change, and delete instances, and everything that `gpu:read` allows | `gpu:write` | -When you create a key in the Fluence Console, give it **View & manage** access to **GPU containers** or **GPU VMs & bare metal**. See [Settings](../settings.md). These options give `akash:write` and `spheron:write`, the scopes of the [legacy GPU API](#legacy-gpu-api). A key with either scope also works with `/v3/gpu`, for reading and for changes. +When you create a key in the Fluence Console, give it **View & manage** access to **GPU containers** or **GPU VMs & bare metal**. See [Settings](../settings.md). These options give `akash:write` and `spheron:write`, the scopes of the [legacy GPU API](#legacy-gpu-api). A key with either scope also works with `/v3/gpu`, for reading and for changes. A key created before your account had GPU access has no GPU scopes. Create a new key. `GET /v3/gpu/offers` and `GET /v3/gpu/offers/{id}` also work without credentials. Without credentials, the list shows only offers that you can rent now. The OpenAPI document needs no credentials either. Every other endpoint returns `401` with `unauthenticated` without credentials. diff --git a/docs/build/api/overview.md b/docs/build/api/overview.md index ad319eb..39782d8 100644 --- a/docs/build/api/overview.md +++ b/docs/build/api/overview.md @@ -67,7 +67,7 @@ Each key has a set of permissions, called scopes, and an expiration date. The AP | Legacy GPU containers (`/gpu`) | | `akash:write` | | Legacy GPU virtual machines and bare metal (`/gpu`) | | `spheron:write` | -- A key can only get scopes that your account has. +- A key can only get scopes that your account has. A key created before your account had GPU access does not get the GPU scopes later. To use the GPU API, create a new key. - A `write` scope does not include the matching `read` scope. To create and then read a VM, a key needs both `vms:write` and `vms:read`. The exception is `gpu:write`, which also allows reading `/v3/gpu`. - A key with `akash:write` or `spheron:write` also works with `/v3/gpu`. The legacy GPU API does not accept read-only scopes: to list or read instances there, a key needs `akash:write` or `spheron:write`. - In the Fluence Console, the **Read only** preset does not include `clusters:read`, `vm:list`, or `prices:read`. A key with only this preset cannot read the catalog or prices. diff --git a/docs/build/overview.md b/docs/build/overview.md index 7f81e93..b187ff4 100644 --- a/docs/build/overview.md +++ b/docs/build/overview.md @@ -33,4 +33,4 @@ The sidebar of the Fluence Console has these sections: ## Pay for compute -A new account can rent GPU and CPU compute right after registration. Rent is charged from your prepaid balance in USD, so top it up first. You can top it up by card or in crypto in the console. An AI agent can also top up over HTTP with USDC through [x402](./api/x402.md). See [Payment and balance management](./balance.md). +GPU Cloud and CPU Cloud are open to every account. Rent is charged from your prepaid balance in USD, so top it up first. You can top it up by card or in crypto in the console. An AI agent can also top up over HTTP with USDC through [x402](./api/x402.md). See [Payment and balance management](./balance.md).