# /geekbench/gpu_results/search

`POST /api/geekbench/gpu_results/search`

Price: 5 credits

Search uploaded Geekbench GPU runs by device, board, chip or vendor name, newest first, within one Geekbench major version. Each row carries the run id and URL, the system and processor name, clock speed and core count, the platform, the graphics API the run measured and its compute score. Feed the id and version to the GPU run endpoint for the workload breakdown and the graphics device detail.

## How to use it

The query reaches the graphics card as well as the host machine, so a card model is the way to assemble runs for one part — 'RTX 5090' returns runs on that card under unrelated system names such as 'ASUS System Product Name'. The card name itself is not on the row; fetch the run to read it. Geekbench calls this family Compute up to version 6 and GPU from 7, and each version is a separate corpus with its own ids. One run measures one graphics API, so read `compute_api` before comparing scores. Rows come back newest first with no relevance ranking and the source offers no API, platform or score filter.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `query` (string, required) — Free text matched against the graphics card, the system name and the processor — a card model, a device model, a board name, a chip name or a vendor (examples: "RTX 5090", "Radeon RX 7900", "Apple M4 Max", "MacBook Pro"; minLength: 1)
- `version` (string) — Geekbench major version to search. Each version has its own corpus and its own id space; runs uploaded under one version never appear under another (default: "6"; one of: "4", "5", "6", "7")
- `count` (integer, required) — Max number of results to return (min: 1; max: 1500)

## Response

### 200 — Successful Response

- `@type` (string) (default: "GeekbenchGpuResultRow")
- `id` (string, required)
- `url` (string, required)
- `version` (string, required)
- `system` (string, nullable)
- `model` (string, nullable)
- `platform` (string, nullable)
- `user` (string, nullable)
- `uploaded_at` (integer, nullable)
- `frequency_mhz` (integer, nullable)
- `core_count` (integer, nullable)
- `details` (object) (default: {})
  - `*` (string)
- `compute_api` (string, 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

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.