Machines

Machine Capabilities

GET/v2/machines/capabilities

Describe every registered provider, and the caller's accelerator access. The provider list is the BUILD's registry, not the deployment's configuration: it names every provider this service knows how to drive, including ones a kill switch has disabled and ones the caller's account is outside the rollout for. Only ``accelerator_requests_enabled`` is scoped to the caller. So this answers "what shape is this provider" — sizes, shared folders, accelerators — and never "may I use it". Agent create is the only authority on that, and it answers 503 for a disabled provider and 403 for one the caller cannot reach. A client that treats presence here as availability builds a picker whose options are then refused.

Request

curl --request GET \
  --url https://api.brainbaselabs.com/v2/machines/capabilities \
  --header 'Authorization: Bearer YOUR_API_KEY'

Response

json

{
  "accelerator_requests_enabled": true,
  "providers": [
    {
      "machine_kind": "string",
      "resource_classes": [
        "cpu"
      ],
      "accelerators": [],
      "supports_shared_folders": true,
      "supported_machine_sizes": [
        "l"
      ],
      "machine_size_resources": {
        "property1": {
          "cpu": 0,
          "memory_gib": 0,
          "disk_gib": 0
        },
        "property2": {
          "cpu": 0,
          "memory_gib": 0,
          "disk_gib": 0
        }
      }
    }
  ]
}