Skip to main content
GET
List CPU types
Required API key scope: catalog:read

Authorizations

Authorization
string
header
required

Runpod API key authentication. Generate an API key in the Runpod console and send it in the Authorization header as Bearer <api_key>. Keys are scoped to the permissions granted when created; requests may return 403 when a valid key lacks access to the requested resource or action.

Console sessions (Clerk JWTs) act for the signed-in user. To act for a team instead, also send X-Team-Id: <team_id>; it applies only when the user owns or belongs to that team, otherwise the request runs against the user's own account. API keys created inside a team already act for that team and do not need the header.

Query Parameters

include
enum<string>[]

Comma-separated optional expansions. Supported value today: AVAILABILITY. This may expand with more include values in the future.

Maximum array length: 1

Catalog include expansion. Only AVAILABILITY is supported today; additional include values may be added in the future.

Available options:
AVAILABILITY
product
enum<string>[]

Comma-separated availability product contexts. Supported values for CPUs: POD, SERVERLESS. Required with include=AVAILABILITY, and valid only with it (400 either way). There is no default: availability differs by product.

CPU catalog product availability context. Availability is product-specific, so this is required whenever availability is requested.

Available options:
POD,
SERVERLESS
Example:
vcpuCount
integer

Availability vCPU count. Valid only with include=AVAILABILITY. Must be a power of two.

Required range: x >= 2

Response

OK

cpus
object[]
required
Last modified on November 18, 2026