# /threedmark/hardware

`POST /api/threedmark/hardware`

Price: 5 credits

Fetch UL's performance rollup for one graphics card or processor. Returns its median 3DMark score across every submitted run, the test that score comes from, its rank in UL's ranking, a five-star performance rating, MSRP, TDP and score per watt, the DirectX feature level of a graphics card or the socket of a processor, a popularity rank from the last 30 days of submissions, and two comparison tables: the closest-priced alternatives with their scores, and the closest-scoring alternatives with their value-for-money rating.

## How to use it

The name must be UL's own spelling with the vendor prefix — 'NVIDIA GeForce RTX 5090', not 'RTX 5090' or '5090' — take names from the ranking endpoint's rows when unsure. Apple Mac systems are listed inside the GPU ranking but only resolve here with `kind=mac`, not `kind=gpu`; pass whichever `kind` the ranking row itself reports rather than assuming everything in that ranking is `gpu`. `score` is the median across every submitted run for that part, which makes it the right number for comparing hardware and useless for reproducing one machine. Which benchmark that median comes from is in `score_test` and it moves as UL retires tests, so compare two parts only when their `score_test` matches. Retail prices are absent: `msrp_price` is the launch price and reads N/A on parts that never had one.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `name` (string, required) — Graphics card or processor model name exactly as UL publishes it (examples: "NVIDIA GeForce RTX 5090", "AMD Ryzen 7 9800X3D"; minLength: 2)
- `kind` (string) — Whether the name is a graphics card, a processor, or an Apple Mac system (ranked inside the GPU listing but reviewed under its own page kind) (default: "gpu"; one of: "gpu", "cpu", "mac")

## Response

### 200 — Successful Response

- `@type` (string) (default: "ThreedmarkHardware")
- `name` (string, required)
- `url` (string, required)
- `kind` (string, required)
- `rating` (integer, nullable)
- `threedmark_rank` (integer, nullable)
- `msrp_price` (string, nullable)
- `directx_level` (string, nullable)
- `socket` (string, nullable)
- `tdp_watt` (number, nullable)
- `score_per_watt` (number, nullable)
- `score` (number, nullable)
- `score_test` (string, nullable)
- `popularity_rank` (string, nullable)
- `details` (object) (default: {})
  - `*` (string)
- `price_comparison` (array) (default: [])
  - `@type` (string) (default: "ThreedmarkHardwarePeer")
  - `name` (string, required)
  - `msrp_price` (string, nullable)
  - `score` (number, nullable)
  - `value_for_money` (number, nullable)
- `closest_rivals` (array) (default: [])
  - `@type` (string) (default: "ThreedmarkHardwarePeer")
  - `name` (string, required)
  - `msrp_price` (string, nullable)
  - `score` (number, nullable)
  - `value_for_money` (number, 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

UL publishes no page for that hardware name

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.