---
title: "Get a CPU type"
method: GET
path: "/v2/catalog/cpus/{id}"
tags: ["Catalog"]
---

# Get a CPU type

`GET /v2/catalog/cpus/{id}`

Returns a single CPU type with pricing. Availability details are included only when requested with include=AVAILABILITY.

## Query parameters

- `include` CatalogInclude[]
- `product` CpuProduct[]
- `vcpuCount` integer

## Response `200`

OK

- CpuType
  - `id` string, required — CPU flavor identifier (use in cpu.id for pod creation)
  - `name` string, required — Human-readable flavor name
  - `group` string, required — CPU generation group
  - `vcpu` object, required
    - `min` integer, required
    - `max` integer, required
  - `ramGbPerVcpu` number, float, required — GB of RAM allocated per vCPU. Multiply by the chosen vCPU count (within `vcpu.min`..`vcpu.max`) to get the total RAM for an instance of this flavor. May be fractional.
  - `price` object, required
    - `securePerVcpu` number, float, required — Price for secure pods per vCPU. Multiply by the chosen vCPU count (within `vcpu.min`..`vcpu.max`) to get the total price.
    - `serverlessPerVcpu` number, float, required — Price for serverless per vCPU. Multiply by the chosen vCPU count (within `vcpu.min`..`vcpu.max`) to get the total price.
  - `availability` 'NONE' | 'LOW' | 'MEDIUM' | 'HIGH' — Catalog stock availability level.
  - `dataCenters` DataCenterAvailability[] — Per-datacenter CPU availability. Present only when requested with include=AVAILABILITY.
    - `id` string, required — Data center identifier.
    - `name` string, required — Human-readable data center name.
    - `availability` 'NONE' | 'LOW' | 'MEDIUM' | 'HIGH', required — Catalog stock availability level.

## Other responses

- `401` — Authentication failed because the bearer token is missing, malformed, expired, or invalid.
- `403` — The bearer token is valid, but it does not grant access to the requested resource or action.
- `404` — The requested resource was not found or is not accessible to the caller.
- `429` — The caller exceeded its per-user rate limit. The response identifies the window that was exceeded and how long to wait. The `RateLimit` and `RateLimit-Policy` headers (per the IETF ratelimit-headers draft) also accompany successful responses, so clients can track quota before a 429.
- `default` — Error

---

[API](https://skmtc.dev/runpod/apis/runpod-rest-api.md) · [All operations](https://skmtc.dev/runpod/apis/runpod-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/runpod/runpod-rest-api/revisions/504cd0394ed6/schema)