/geekbench/users

POST /api/geekbench/users

Price: 5 credits

Fetch a Geekbench Browser uploader profile by username, with every run they have published. Each run carries its id and URL, which Geekbench version and which family it belongs to, the machine and processor, platform and architecture, and the scores that family reports — single-core and multi-core for CPU runs, the compute score and its graphics API for GPU runs, and the three precision scores for AI runs. A per-section tally of how many runs each version and family holds comes with it.

How to use it

The username is not case-sensitive, but it exists only where the uploader signed the run, and most uploads are anonymous — search rows carry a `user` on 10 of 25 version-2 rows, 5 of 25 on version 3, 2 of 25 on version 4 and none at all on versions 5 to 7, so the modern search is not where profile names come from. The whole profile arrives in one response with no paging, so a prolific uploader returns several hundred runs at once. An id from here is fetchable with the matching run endpoint using the run's own `version` — the same number under a different version is a different run.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• alias string required — Geekbench Browser username, the segment of a browser.geekbench.com/user/ URL (examples: "gemino", "elmor"; minLength: 1)

Response

• @type string (default: "GeekbenchUser")
• alias string required
• url string required
• name string required
• result_count integer (default: 0)
• result_counts object (default: {})
  • * integer
• results array (default: [])
  • @type string (default: "GeekbenchUserResult")
  • 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
  • kind string required
  • architecture string nullable
  • compute_api string nullable
  • framework string nullable
  • backend string nullable
  • single_core_score integer nullable
  • multi_core_score integer nullable
  • compute_score integer nullable
  • single_precision_score integer nullable
  • half_precision_score integer nullable
  • quantized_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 profile exists for that username 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.