/geekbench/cpu_results

POST /api/geekbench/cpu_results

Price: 1 credit

Fetch one uploaded Geekbench CPU run by its id. Returns the single-core and multi-core scores, the per-workload breakdown with each workload's own score and throughput figure, the uploader, the upload time and view count, and the machine it ran on: operating system, model and model identifier, motherboard, processor name, identifier, topology, clock speeds and caches, and memory size, type and channels. Geekbench 2 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 CPU family, so `version` is part of the key, not a hint: id 19105235 is a real run under version 6 and does not exist under 7, and an id belonging to a GPU run resolves to an unrelated CPU run rather than failing. Take both values from the same search result rather than pairing an id with a guessed version. Version 2 differs in kind: it reports one figure in `overall_score` plus Integer, Floating Point, Memory and Stream section scores, and no single-core or multi-core pair. Versions 3 to 7 all fill `single_core_score` and `multi_core_score`, but the workloads behind them changed with every version, so those numbers compare only within one version.

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 CPU run, as it appears in the browser.geekbench.com URL (examples: "19105235", "258598", "2744866"; 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: "2", "3", "4", "5", "6", "7")

Response

• @type string (default: "GeekbenchCpuResult")
• 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
• single_core_score integer nullable
• multi_core_score integer nullable
• overall_score integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit 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 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 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 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 Wait at least 30 seconds, then retry.

Response 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.