Every benchmark in the database, newest first; the payloads are read but not returned — the summary is computed from them here.

q is applied after the owners are resolved so that searching by e-mail works — the owner lives in another database and cannot be joined against. That is also why limit caps the RESULT rather than the read: limiting the read first would hide a client's older benchmarks from their own e-mail search and answer "none found", which is the one answer this endpoint must never give wrongly. MAX_ADMIN_SCAN bounds the read instead.