# /geekbench/gpu_results

`POST /api/geekbench/gpu_results`

Price: 1 credit

Fetch one uploaded Geekbench GPU run by its id. Returns the compute score under the graphics API the run used (Metal, OpenCL, Vulkan or CUDA), the per-workload breakdown with each workload's score and throughput figure, the graphics device name, vendor, memory, clock and compute-unit count, and the host machine: operating system, model, motherboard, processor, clocks, caches and memory. Geekbench 4 through 7 are covered, and every information row the page carries is returned verbatim alongside the named fields.

## How to use it

Ids are scoped to one Geekbench version and to the GPU family, so `version` is part of the key, not a hint: an id belonging to a CPU run resolves to an unrelated GPU run rather than failing, and an id that also exists under a different version resolves there too, as a different machine, rather than answering 404 or 412. Take both `id` and `version` from the same search result rather than pairing an id with a guessed version. Geekbench calls this family Compute up to version 6 and GPU from 7; both are served here under the same `version` field. One run measures one graphics API, so a machine with Metal, OpenCL and Vulkan results has three separate runs with three ids, and `compute_api` tells you which one you got — scores are not comparable across APIs.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `id` (string, required) — Numeric id of the uploaded GPU run, as it appears in the browser.geekbench.com URL (examples: "6860837", "124214", "5322002"; minLength: 1)
- `version` (string) — Geekbench major version the run was uploaded under. Each version keeps its own id space, so the same number addresses a different run under a different version (default: "6"; one of: "4", "5", "6", "7")

## Response

### 200 — Successful Response

- `@type` (string) (default: "GeekbenchGpuResult")
- `id` (string, required)
- `url` (string, required)
- `version` (string, required)
- `system_title` (string, nullable)
- `uploaded_at` (integer, nullable)
- `view_count` (integer, nullable)
- `user` (string, nullable)
- `benchmark_version` (string, nullable)
- `validation` (string, nullable)
- `operating_system` (string, nullable)
- `system_model` (string, nullable)
- `system_model_id` (string, nullable)
- `motherboard` (string, nullable)
- `cpu_name` (string, nullable)
- `cpu_identifier` (string, nullable)
- `cpu_topology` (string, nullable)
- `cpu_processor_count` (integer, nullable)
- `cpu_core_count` (integer, nullable)
- `cpu_thread_count` (integer, nullable)
- `cpu_base_frequency_mhz` (integer, nullable)
- `cpu_max_frequency_mhz` (integer, nullable)
- `memory_size_gb` (number, nullable)
- `memory_type` (string, nullable)
- `memory_channel_count` (integer, nullable)
- `scores` (object) (default: {})
  - `*` (integer)
- `information` (array) (default: [])
  - `@type` (string) (default: "GeekbenchInfoSection")
  - `name` (string, required)
  - `details` (object) (default: {})
    - `*` (string)
- `benchmarks` (array) (default: [])
  - `@type` (string) (default: "GeekbenchBenchmarkSection")
  - `name` (string, required)
  - `score` (integer, nullable)
  - `workloads` (array) (default: [])
    - `@type` (string) (default: "GeekbenchWorkload")
    - `name` (string, required)
    - `score` (integer, nullable)
    - `measurement` (string, nullable)
    - `accuracy` (string, nullable)
- `compute_api` (string, nullable)
- `gpu_name` (string, nullable)
- `gpu_vendor` (string, nullable)
- `gpu_memory` (string, nullable)
- `gpu_max_frequency_mhz` (integer, nullable)
- `gpu_compute_unit_count` (integer, nullable)
- `compute_score` (integer, nullable)

## 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

No run with that id under that Geekbench version, or the upload is withheld because it ran on unreleased hardware

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.