Before you start, ensure you have set your API keys and SSH key path as outlined in the CLI introduction.
Retrieving GPU Availability Data
To see all available GPU types and their current pricing across all regions, simply run:Retrieving Disk Availability Data
To see all available disk storage options across providers and datacenters:Retrieving Filtered GPU Availability Data
You can then use filters like--gpu-type, --regions, or --gpu-count to narrow down the results. Here are all available filters:
GPU Availability Filters
-
--gpu-type: Filter by specific GPU model- Example:
--gpu-type H100_80GB - Optional string value
- Example:
-
--gpu-count: Filter by number of GPUs- Example:
--gpu-count 2 - Optional integer value
- Example:
-
--regions: Filter by geographic regions- Example:
--regions united_states,canadaor--regions united_states --regions canada - Optional, can specify multiple regions
- Example:
-
--socket: Filter by socket type- Example:
--socket PCIe - Accepts values:
PCIe,SXM2,SXM3,SXM4,SXM5 - Optional string value
- Example:
-
--disks: Filter GPUs by disk IDs (shows GPUs in same location as disks)- Example:
--disks disk-id-1 --disks disk-id-2 - Optional, can specify multiple disk IDs
- Useful for finding GPUs compatible with your existing disks
- Example:
-
--group-similar: Group similar configurations from same provider- Example:
--no-group-similar - Default: true
- Optional boolean flag
- Example:
Example with Multiple Filters
Finding GPUs Compatible with Your Disks
If you have existing disks and want to find GPUs in the same datacenter/region:Retrieving Filtered Disk Availability Data
Disk Availability Filters
-
--regions: Filter by geographic regions- Example:
--regions united_states,eu_north - Optional, can specify multiple regions
- Example:
-
--data-center-id: Filter by specific datacenter- Example:
--data-center-id US-1 - Optional string value
- Example:
-
--cloud-id: Filter by cloud configuration ID- Example:
--cloud-id "Provider Storage A" - Optional string value
- Example:
Example with Filters
Understanding the Terminal Output
GPU Availability Output
Here’s an example of what the command output looks like:| ID | GPU Type | GPUs | Socket | Provider | Location | Stock | Price/Hr | Memory (GB) | Security | vCPUs | RAM (GB) |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 346663 | H100_80GB | 2 | PCIe | runpod | CA | Low | $5.40 | 160 | secure_cloud | 32 | 502 |
| 551ffd | H100_80GB | 2 | PCIe | runpod | US | Low | $5.40 | 160 | secure_cloud | 32 | 502 |
- A unique ID for the configuration
- GPU specifications (type, count, socket)
- Provider and location information
- Current stock status
- Pricing and hardware details
Disk Availability Output
For disk availability, the output includes:| ID | Provider | Location | Stock | Price/Hr/GB | Max Size (GB) | Is Multinode |
|---|---|---|---|---|---|---|
| 7d2232 | runpod | US (US-WA-1) | Available | $0.00011111 | 8192 | Yes |
| 472b26 | hyperstack | NO (NORWAY-1) | Available | $0.00009700 | 100000 | No |
- A unique ID for the configuration
- Provider offering the storage
- Location (country and datacenter)
- Stock availability status
- Price per GB per hour
- Maximum disk size supported
- Whether the disk supports multinode (can be attached to multiple instances)