An AI has won the Metaculus Cup for the first time
Two stories this hour about machines doing human work in public, and one of them came with a scoreboard.
An AI system won the seasonal Metaculus Cup on September 5 — the first time a bot has taken the top spot in the forecasting tournament that humans have owned since it began. The Economist reports that AI entries also took second and fifth place, pushing humans into third and fourth. Hundreds of entrants had to call questions resolving by September: whether an American state or EU country would restrict data-center construction, how the hantavirus outbreak would spread off the MV Hondius, where Brent crude would settle. Scoring rewarded staying closest to the truth for the longest, and the humans split a $5,000 prize pool that is smaller than what the fifth-placed AI had already made trading on its own forecasts.
The winner wasn't a lab. It was built by Jeffrey Liang, a self-described polymath in Texas, who told the Economist he spent under 150 hours and a couple of thousand dollars on compute and data — beating four startups that raised more than $15 million between them. The commercial numbers are stranger still: FutureSearch has gained 6% since June on a $100,000 Kalshi portfolio betting where its AI thinks the market is wrong, while one of Preseen's developers turned $35 into $1.94 million over seven months on the same platform, the sixth-best return in Kalshi's history.
Why it matters is less about the trophy than the unit economics underneath it. A forecast from a team of human superforecasters costs more than $10,000 and takes about a week; FutureSearch sells ten minutes for a few dollars. That gap turns a service only hedge funds and governments could buy into something you can run while reading the news — and it turns forecasting into the first white-collar task where the cheap version is not visibly worse. The Forecasting Research Institute already concluded in July that AI systems have reached parity with superforecasters, and the 2015 work that defined the category — Barbara Mellers and colleagues on how superforecasters see 300 days out as reliably as ordinary forecasters see 60 — now reads like a baseline rather than a ceiling.
The counter-case is real, and it lives in the timeframe. Metaculus's cup tests a four-month horizon, not the multi-year geopolitical calls institutions actually pay for, and Mantic's Yann Riviere still gives humans the edge there. Read the ticker, too: a seasonal tournament is one sample with heavy luck attached, which is why a single win is a signal, not a coronation. Watch whether the AI-only Metaculus competition now running — $50,000 on the line, with Liang's bot leading — produces a repeat rather than a one-off.
Tencent released WeVisDoc, a pair of small open document parsers that beat the specialized competition on the benchmark that matters for this task. Fine-tuned from Qwen3-VL-2B and Qwen3-VL-4B, the models take a page image and return structured Markdown with LaTeX formulas and HTML tables intact. The 4B version scores 95.38 overall on OmniDocBench v1.6 and a mean of 75.54 across the three PureDocBench tracks, ranking first among the compared end-to-end parsers in all four settings, averaged over three inference runs.
The significance is the size. Document parsing has mostly been a pipeline: layout detection, then table recognition, then formula OCR, then glue. WeVisDoc collapses that into one vision-language model you can run at 2B or 4B parameters — small enough to self-host, and open enough that the comparison table is checkable. If the numbers hold outside the leaderboard, this is the kind of model that quietly replaces a multi-stage stack inside a company's data pipeline, which is where most enterprise document AI still breaks.
What to watch: whether the PureDocBench lead survives independent runs, and how the 2B version — the one small teams will actually deploy — holds up on scans and handwriting rather than clean PDFs.
Would you trust a model's probability over a human analyst's judgment on a call your money depends on? Tell us in the comments.
Sources: WeVisDoc (GitHub)
