GPU resource status

Understand the available GPU interfaces and confirm that a reported resource has a real allocation backend.

Open GPU Resources

Check the resource origin

GPU screens and API families serve different records. The /api/gpu/resources implementation generates sample resources in development and currently returns an empty production list. Treat those samples as demonstration data.

The GPU dashboard and registration interfaces have separate resource records. Confirm the backend, node, allocation state, and returned telemetry for the specific workflow you use.

Before running a workload

  1. Inspect the selected resource and its actual allocation status.
  2. Confirm that the workload runtime can access the GPU and required libraries.
  3. Run a small validation workload and inspect its logs before assuming training or inference is accelerated.

API endpoints

Use your Genorbex deployment’s origin followed by the path below. Replace IDs with resources accessible to your account. Authentication and permissions are checked by each endpoint.

GET /api/gpu/resources

Returns generated development resources or the current production resource list.

Authentication: Genorbex account token and service/resource access; API-key support follows the endpoint’s authentication guard.

Need help with your setup? Visit the Help Center or contact Genorbex.