Skip to main content

Authentication

Runpod uses API Keys for all API requests. Go to Settings to manage your API keys.

GraphQL API spec

If you need detailed queries, mutations, fields, and inputs, look at the GraphQL spec.

Create Pods

A Pod consists of the following resources:
  • 0 or more GPUs - A pod can be started with 0 GPUs for the purposes of accessing data, though GPU-accelerated functions and web services will fail to work.
  • vCPU
  • System RAM
  • Container Disk
    • It’s temporary and removed when the pod is stopped or terminated.
    • You only pay for the container disk when the pod is running.
  • Instance Volume
    • Data persists even when you reset or stop a Pod. Volume is removed when the Pod is terminated.
    • You pay for volume storage even when the Pod is stopped.
  • Global Networking

Create on-demand Pod

Create spot Pod

Filter by CUDA version

You can pass in the allowedCudaVersions as a list of CUDA versions that you want to allow for the GPU in the pod. This helps in specifying the compatible CUDA versions for your GPU setup.

Start Pods

Start on-demand Pod

Start spot Pod

Filter by CUDA version

You can pass in the allowedCudaVersions as a list of CUDA versions that you want to allow for the GPU in the pod. This helps in specifying the compatible CUDA versions for your GPU setup.

Stop Pods

List Pods

List all Pods

Get Pod by ID

List GPU types

When creating a Pod, you will need to pass GPU type IDs. These queries can help find all GPU types, their IDs, and other attributes like VRAM.

Get GPU type by ID

Check GPU type availability

You can check if a specific GPU type is available in the Secure Cloud or Community Cloud.
The stockStatus field can help you determine the likelihood that a particular GPU type will be available when creating a Pod. For example, if stockStatus is "Low", it means there are very few GPUs of that type available.