Mean match score across the same talent GET /talents/count would count, with the same filter/vectors/proximity/audience parameters and the same visibility rules. Split off the count (POOL-2184) because averaging needs a per-document value and so can never be answered from the index, which made every talent-table tile render read the whole tenant. Only the vector-scoring stages write score, so a query without vectors returns null — including a proximity-only query, since proximity compiles to a bare $geoWithin $match that filters but writes no score.