Repository navigation
docs: describe GPU Cloud API v3, spot instances and the new GPU cloud console section - #146
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
justprosh
marked this pull request as ready for review
November 13, 2026 16:59
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
build/api/gpu_cloud.md): rewritten for/v3/gpu. Covers scopes, the offer endpoints (offers, groups, facets, picks), quotes, creating instances withIdempotency-Key, the instance lifecycle, rename and container updates, logs and events, deletion, and errors. The legacy/gpuAPI moves to a short section at the end. The old/gpu/api-docsreference link returns 404, so it is removed.build/gpu_cloud/overview.md): adds offers and providers, on-demand and spot instances, and the/v3/gpustatuses. Billing now uses the offer's billing step and minimum charge in place of hourly charges.gpu:readandgpu:write.charged.totalis final, in the same words on the concepts, manage, and API pages./v3/gpu.offerKind,hostTier,availability,preemption,capabilities,provisioning,osImages),rejectedandlargestOnSaleof offer picks, the quote response, instance fields (statusDetail,isBilling,placement,charged,actions), list filters,fleet_too_largeand other common error codes,X-Request-Id, andGET /v3/gpu/openapi.json.How each fact was checked
https://api.fluence.dev/v3/gpu/openapi.json(version 3).GET /v3/gpu/offersresponses on 2026-11-13.noticeSeconds: 0anddataSurvives: false.GET /v3/gpu/offers,GET /v3/gpu/offers/{id}, andGET /v3/gpu/openapi.jsonreturn200.offer-facets,offer-picks,default-images,instances, andvolume-offersreturn401.capabilities.volumes: 0.market_profile, Lium offers arehost_offer, other providers areprovider_sku.401fromGET /v3/gpu/instances./gpustill answers: observed.GET /gpu/plans/returns401without a key, andGET /gpu/default-images/returns200.Not verified
/v3/gpu: thatakash:writeandspheron:writekeys work on/v3/gpucomes from the service team and the backend code. No live call was made./gpuinstances use the same billing step and minimum comes from the service team.nodesfilter and requirement, but production refusesnodeswithinvalid_input. Clusters are left out of the page.failed, and that a running instance that stops being ready stays billed until deleted, comes from the service team. It was not observed.gpuModelreturns an empty list. That a quote or a create request returnsinvalid_inputcomes from the service team.