# /geekbench/charts

`POST /api/geekbench/charts`

Price: 10 credits

Read one of Geekbench's published benchmark charts: the desktop and laptop processor ranking, the Android, iOS and Mac device rankings, the Metal, OpenCL and Vulkan graphics rankings, or the Geekbench AI device ranking. Each row carries the hardware name, its position in the chart, the aggregate score behind it and how many uploads that aggregate was computed from, the chip or clock description, and its microarchitecture or vendor family. Rows on the processor and device charts also carry the slug that fetches that chip's or device's own rollup, except where the name alone cannot be resolved to one specific configuration, which the endpoint leaves without a slug rather than guessing.

## How to use it

This is the slug inventory for the processor and device endpoints: nothing else on the site lists them, and they are not derivable from a product name. Rows come back ranked by score, highest first, so `count` takes the top N and `rank` is that position, and which score fields are populated depends on the chart — the processor and device charts carry single-core and multi-core, the iOS chart adds Metal on effectively every row, the Android chart adds OpenCL or Vulkan on a majority of rows, the Mac chart adds Metal or OpenCL on a minority of rows but never Vulkan, the graphics charts (metal/opencl/vulkan) carry their one score in `single_core_score` rather than in a field named after the chart's own compute API, and the AI chart carries three precisions in `scores`. The Android chart returns devices the site's own ranking page leaves out, so a name missing from the published chart may still be here.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `chart` (string, required) — Which benchmark chart to read: processor for desktop and laptop CPUs, android, ios and mac for devices, metal, opencl and vulkan for graphics devices under that API, ai for the Geekbench AI device ranking (one of: "processor", "android", "ios", "mac", "metal", "opencl", "vulkan", "ai")
- `count` (integer, required) — Max number of chart rows to return, taken from the top of the chart (min: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "GeekbenchChartEntry")
- `chart` (string, required)
- `rank` (integer, required)
- `name` (string, required)
- `alias` (string, nullable)
- `url` (string, nullable)
- `description` (string, nullable)
- `family` (string, nullable)
- `icon` (string, nullable)
- `compute_api` (string, nullable)
- `sample_count` (integer, nullable)
- `single_core_score` (integer, nullable)
- `multi_core_score` (integer, nullable)
- `metal_score` (integer, nullable)
- `opencl_score` (integer, nullable)
- `vulkan_score` (integer, nullable)
- `scores` (object) (default: {})
  - `*` (integer)

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.

### 412

The entity was not found, or a precondition failed

What to do: Retrying will not help: either the entity does not exist, or the input points at a different one.

### 429

Too many requests: a rate limit or a usage window is exhausted

What to do: When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.

### 500

Something broke on our side

What to do: Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.

### 529

Rate limit reached, or the endpoint is overloaded

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these headers:

- `X-Error` — Error message text (present only on error)
- `X-Request-ID` — Unique request identifier
- `X-Execution-Time` — Execution time in seconds
- `X-Result-Count` — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
- `X-Total-Available-Results` — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
- `X-Warning` — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
- `X-Retry-After` — Seconds to wait before retrying. Present only on 429.