/vesa/clearmr/products

POST /api/vesa/clearmr/products

Price: 10 credits

List the displays VESA has certified under ClearMR, the motion-blur programme that scores a panel by its clear-to-blur pixel ratio. Narrows by a keyword matched against manufacturer and model and by a tier range. Returns the manufacturer, the certified model with the sibling SKUs the certificate also covers, screen size, resolution, the frame rate the measurement was taken at, and the numeric ClearMR tier.

How to use it

`tier` is the numeric ClearMR score, higher meaning less perceived motion blur, and it is a free number rather than a fixed ladder — bound it with `min_tier`/`max_tier` instead of matching an exact value. A single registry row often names several SKUs; the first is `model` and the rest are `aliases`, so match a part number against both. `frame_rate` is the refresh the measurement was taken at, not the panel's maximum. The registry lists only what a vendor asked VESA to publish, so absence is not evidence a display is uncertified.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• search string nullable — Case-insensitive substring matched against the manufacturer and the model (examples: "AOC", "AG276QKD", "Samsung"; minLength: 1)
• min_tier integer nullable — Lowest ClearMR tier to return, as the numeric score the registry prints (min: 0)
• max_tier integer nullable — Highest ClearMR tier to return, as the numeric score the registry prints (min: 0)
• count integer required — Max number of results to return (min: 1; max: 1000)

Response

• @type string (default: "VesaClearMrProduct")
• certificate_id string nullable
• manufacturer string nullable
• model string nullable
• screen_size string nullable
• resolution string nullable
• frame_rate string nullable
• tier integer nullable
• product_url string nullable
• aliases array (default: [])

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 certified display matched the keyword and tier range 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.