# /geekbench/cpu_results/search

`POST /api/geekbench/cpu_results/search`

Price: 5 credits

Search uploaded Geekbench CPU 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 upload time and the single-core and multi-core scores — the single overall score on version 2. Feed the id and version to the CPU run endpoint for the full workload breakdown and machine detail.

## How to use it

The query reaches both strings the machine reported: 'iPhone 17 Pro' matches on the device and 'Ryzen 9 9950X' on the chip, and a chip query is the reliable one because desktops usually report a board string such as 'ASUS System Product Name' or 'QEMU Standard PC' with no product name in it. `version` picks a separate corpus rather than filtering one: version 6 and 7 hold different runs of the same machines, and a run found here is addressable only under the version it was found in. Rows come back newest first with no relevance ranking, and the source offers no date, platform or score filter, so narrow by making the query more specific rather than by asking for more rows.

## 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 uploaded system name and the processor name — a device model, a board name, a chip name or a vendor (examples: "iPhone 17 Pro", "Apple M4 Max", "Ryzen 9 9950X", "ASUS ROG"; 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: "2", "3", "4", "5", "6", "7")
- `count` (integer, required) — Max number of results to return (min: 1; max: 1500)

## Response

### 200 — Successful Response

- `@type` (string) (default: "GeekbenchCpuResultRow")
- `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)
- `architecture` (string, nullable)
- `single_core_score` (integer, nullable)
- `multi_core_score` (integer, nullable)
- `overall_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.