- 01
Verified benchmarks only
Every run counted comes from a public, published study on a benchmark the hub has verified and listed. Nothing else is counted.
- 02
One outcome, the benchmark's own
Every run is graded by the benchmark's own answer key or checks, or by the benchmark's own checks: a pass is that verdict, and a run that did not finish counts as a fail.
- 03
Typical (median) spend per passing run
The median spend of a passing run on cost, tokens and time, against every setup that passed the same tasks: 100 = the lowest typical (median) spend per passing run, task by task. Spend per pass is shown beside it and is not in the score; the two can order setups differently, because efficiency compares the typical (median) passing run, task by task, while spend per pass averages every attempt, so a few very expensive runs, passing or not, count in full; and spend per pass also counts the attempts that failed or did not finish, and divides by the pass rate.
- 04
Compare like with like
A setup is compared only with setups scored on the same benchmarks and the same tasks, and setups the data cannot separate share a band. “#1” is printed only when there are at least 2 compared benchmarks and more than one setup scored on every one of them, and the lead among those setups is separated from every other, holds with any one benchmark left out, and does not come from efficiency alone.