Reliability API

Tested against published outcomes

Before anyone relies on a verdict, it helps to see the method reach answers that someone else has already published.

How the test works

Each set is a group of claims whose outcome someone else has published. Every claim was run through the ordinary method with the published answer hidden from it. Only then was each verdict set beside the published outcome.

Case studies

Elon Musk’s self-driving timelines

26 dated predictions. The outcome comes from Wikipedia’s list, CC BY-SA 4.0. They either happened or did not, and news reports say so.

The case study

Seoul AI safety commitments

19 promises, one per company: publish a safety framework by the Paris summit. The outcome comes from METR’s list. Frameworks are published documents with dates.

The case study

White House AI commitments, 2023

56 promises by 16 companies, scored by Wang et al. 2025, CC BY 4.0. It mostly tests whether evidence exists outside the answer key: the reference scores what companies said they did, and the method asks for the deliverable itself.

The numbers

“Right direction”: take the claims where both the published record and the machine gave a clear answer, kept or not kept. How often did they give the same answer?

“Same verdict” is stricter: how often the machine’s answer matched exactly, including how sure it was. “Resolved false” beside “not met” counts; “mostly false” beside “not met” does not.

“Unresolvable”: claims where the machine found too little dated evidence to decide, so it gave no verdict rather than guess.

Machine verdicts beside published outcomes, by set
SetRight directionSame verdictUnresolvable
Musk22 of 2221 of 260
Seoul14 of 1411 of 184
White House18 of 2013 of 5623

Every verdict in these sets is machine-generated and not yet reviewed by a person.