BENCHMARK · SNAPSHOT ri-20261025-1526

Does the judgment hold up?

If a judgment is the product, its error rate is part of the product. These are all 28 cases from one run against the live endpoint — including the ones it abstained on and the one control we could find.

28auditable cases
15/15direct retractions caught
0contaminated called clean
8abstentions
2,158 mslatency p50
2,987 mslatency p95
0.46mean reference coverage

01 METHOD

The labels are not our opinion; they are computed from the snapshot by construction:

  • A — the paper itself carries an A-tier notice (a retraction registered against its DOI). Expected verdict: CONTESTED.
  • B — one of its references is retracted. Expected: CONTESTED, or an abstention. Calling it SUPPORTED is a false negative.
  • C — no retracted work within two citation hops. Only SUPPORTED counts as correct.

Every case is a real call to the production retraction_propagation tool on 2026-10-28 against snapshot ri-20261025-1526. Latency is client wall-clock time including the public network round trip.

02 THE CASES (click for the graph)

GroupDOIVerdictConf.Cov.Rootsms
DEPTH010.1016/j.saa.2015.02.011CONTESTED0.500.0011817
DEPTH010.1083/jcb.200501040CONTESTED0.500.0012050
DEPTH010.1182/blood-2008-01-133710CONTESTED0.500.0012019
DEPTH010.1016/s0092-8674(03)00436-7CONTESTED0.500.0012024
DEPTH010.1016/j.jacc.2011.12.043CONTESTED0.500.0011921
DEPTH010.2337/db13-1526CONTESTED0.500.0012289
DEPTH010.1074/jbc.m611728200CONTESTED0.500.0012125
DEPTH010.1073/pnas.0610590104CONTESTED0.500.0011781
DEPTH010.1038/nature26142CONTESTED0.500.0012026
DEPTH010.1038/s41417-022-00501-1CONTESTED0.500.0011736
DEPTH010.1016/j.jcrysgro.2005.05.065CONTESTED0.500.0012060
DEPTH010.1001/jama.293.9.1082CONTESTED0.500.00124704
DEPTH010.1128/jvi.76.13.6815-6824.2002CONTESTED0.500.0011657
DEPTH010.1038/ncb942CONTESTED0.500.0012197
DEPTH010.1038/35099527CONTESTED0.500.0011922
DEPTH110.1161/cir.0000000000001052ABSTAINED0.501.00102542
DEPTH110.1161/cir.0000000000000558ABSTAINED0.501.0022327
DEPTH110.1161/cir.0000000000000485ABSTAINED0.501.0032430
DEPTH110.4158/ep161365.glCONTESTED0.990.9932368
DEPTH110.1161/cir.0000000000000350ABSTAINED0.501.0032244
DEPTH110.1161/cir.0000000000000152CONTESTED1.001.00224640
DEPTH110.1161/cir.0000000000000152CONTESTED1.001.0022987
DEPTH110.1161/01.cir.0000441139.02102.80ABSTAINED0.500.9921979
DEPTH110.1097/01.hjh.0000431740.32696.ccCONTESTED1.000.9942226
DEPTH110.1161/str.0000000000000046ABSTAINED0.501.0042530
DEPTH110.36660/abc.20201238ABSTAINED0.480.9782370
DEPTH110.1161/str.0000000000000024ABSTAINED0.501.0042192
CLEAN10.3748/wjg.11.7461SUPPORTED1.001.0001595

03 WHAT IT CANNOT DO

There is no clean control group. The snapshot is a retraction neighbourhood: harvesting started from retracted seeds and walked their citations, so almost everything in it is inside the contamination radius. Only one true control survived. This benchmark therefore shows recall and non-fabrication, not precision on clean literature. Fixing that needs a control harvest (about a day of API budget) and is the next version of this page.

Abstaining is a feature. Eight of the twelve citing-retracted cases abstained, all with single_aggregator_source: only the C-tier aggregator claimed a retraction and no A-tier notice backed it. We refuse to promote an aggregator flag to a fact.

Coverage is the ceiling. Mean reference coverage is 0.46; below 0.5 the tool abstains outright. More conclusions require more data, not a different model.

04 REPRODUCE IT

The judgment is a deterministic graph query: the same DOI on the same snapshot always returns the same answer.

Anonymous MCP, no key needed, 20 requests/minute per IP:

curl -s -X POST https://mcp.ashesborn.cloud/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"bench","version":"1"}}}'

Free status lookup, no key: ashesborn.cloud/datasets · GET https://pay.ashesborn.cloud/api/v1/judge/paper?doi=<doi>

Raw run output — 28 records, verdicts, roots, coverage and latency as measured.

Full judgments with the per-hop evidence path are metered at $0.02 / $0.10, no signup: POST https://pay.ashesborn.cloud/api/v1/judge