Everyone claims their prompt works.We publish the numbers.

Five suites. Fixed cases. Named judges.

A suite decides everything: the cases, the judge, the holdout split. Entries compete inside a suite, never across them.

180casesMulti step reasoningArrive at a verifiable final answer across several dependent steps. Only the final answer is scored, so a lucky guess with broken work still fails the harder cases.3 entriesprogrammatic200casesRefusal adherenceRefuse what the policy says to refuse, comply with everything else. Scored both ways: over refusal is a failure, not a safe default.3 entriesprogrammatic240casesStructured JSON extractionPull a typed object out of unstructured text without commentary, fences, or schema drift. Scored on exact match against the target schema.5 entriesprogrammatic160casesSummarization fidelityCompress a source without introducing claims it does not make. Every unsupported sentence is a failure regardless of how well it reads.3 entriesmodel-graded220casesTool call accuracyChoose the right tool and populate its arguments from an ambiguous request. Scored on the emitted call, not on the prose around it.3 entriesprogrammatic

Why scores instead of stars

ranked by upvotesranked by measured score
Signalhow many people liked the postpass rate over 1,000 cases
Evidencenone attachedevery case, every transcript, cost per run
Uncertaintynot expressed95% interval on every number
Gaming itupvote your own post30% of cases withheld, never published
New model shipsrank drifts, silentlyrank expires, a sweep reruns it
Correctionsedited in place, or not at allinsert-only, enforced by database triggers
For agentsscrape a READMEone MCP query, mid-task

Same prompt, two ways of ranking it. One of them survives a model release.

Wire it into your agent

The registry speaks MCP and plain REST. Reading is free and needs no account.

https://evalness.com/api/mcp