/geekbench/processors

POST /api/geekbench/processors

Price: 1 credit

Fetch one processor's Geekbench rollup by its slug. Returns the chip specification — base and maximum frequency, core, performance-core, efficient-core and thread counts, base and maximum power, microarchitecture codename and socket package — together with the single-core and multi-core scores aggregated across every run uploaded for that chip, and the ranked comparison tables the page shows against other processors of the same family, each peer carrying its own slug so it can be fetched in turn.

How to use it

The slug is not derivable from a marketing name — take it from the processor benchmark chart or from a peer row's `alias` here, since punctuation and suffixes vary ('intel-core-i9-14900k' but 'snapdragon-x2-elite-extreme-x2e-96-100'). Scores here are the chip's aggregate across all uploads, not one run, so they are the right number for comparing hardware and the wrong one for reproducing a specific machine. Desktop, laptop and Apple-silicon Mac chips have a page here ('apple-m4-max' resolves); phone and tablet SoCs do not ('apple-a19-pro' does not), and those are reached as devices instead.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• alias string required — Processor slug from a browser.geekbench.com/processors/ URL, as returned by the processor benchmark chart (examples: "intel-core-i9-14900k", "apple-m4-max", "snapdragon-x2-elite-extreme-x2e-96-100"; minLength: 1)

Response

• @type string (default: "GeekbenchProcessor")
• alias string required
• url string required
• name string required
• codename string nullable
• package string nullable
• frequency_mhz integer nullable
• max_frequency_mhz integer nullable
• core_count integer nullable
• performance_core_count integer nullable
• efficient_core_count integer nullable
• thread_count integer nullable
• base_power_watt integer nullable
• max_power_watt integer nullable
• single_core_score integer nullable
• multi_core_score integer nullable
• scores object (default: {})
  • * integer
• details object (default: {})
  • * string
• charts array (default: [])
  • @type string (default: "GeekbenchComparisonChart")
  • name string required
  • rows array (default: [])
    • @type string (default: "GeekbenchChartRow")
    • name string required
    • alias string nullable
    • url string nullable
    • description string nullable
    • score integer nullable
    • scores object (default: {})
      • * integer

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 processor page exists for that slug 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.