Proof: which workers did the best work, and what it cost

Every model that has taken a seat in Auteur's own construction, ranked from the receipts. This is the dataset behind the governed build-campaign demonstration on the home page, and it is the same ledger the studio reads when it picks a seat for the next round.

Two words carry the whole table. Finished means an attempt ended done and passed the tests its task declared; nothing else counts. Tries counts every attempt, including the ones verification stopped. A caught failure is the product working, so the low rows stay on the page.

Paid seats are metered in dollars by their provider, to the cent. Subscription seats are the flat-rate plans you already carry, so there is no dollar to show for a task and we do not invent one: they are measured in tasks, minutes and new tokens instead.

Receipts, not vibes · measured 2026-11-05

Paid seats, metered in dollars

Why "not enough data" on a paid row: a cost per finished task is only shown when every try reported its spend. A silent try makes the ratio a guess, and guesses are not published as measurements. Why the low pass rates are on the page: a caught failure is the product working. Those tries were stopped by verification before anything shipped.

Subscription seats, measured in tasks, minutes and tokens

"New tokens" is what the model read or wrote for the first time. Cache re-reads are the provider's discount, not our work, so they are not counted. Rows under 20 tries are dimmed: a perfect score from a handful of attempts is a hint, not a fact.

Read from the operator dashboard on 2026-11-05. Live counters; they keep moving as builds complete.

How to read this honestly

More effort is not more finish. The same model at its highest reasoning setting finished fewer of its tries and took three times as long as it did at a high setting. That is one model's record, not a law: Auteur's seat selection is drawn from rows like these, not from a leaderboard someone else ran on a benchmark that is not your work.

A cost per finished task is only shown when every try reported its spend. A partial sum divided by a full count would understate the true cost, so the column reads "not enough data" until the coverage is complete.

Cache re-reads are not counted as work anywhere on this page. When a provider serves a token from cache it is that provider's discount, on every tool that uses the same model, so it belongs to them and not to us.

How trust works here · OpenRouter seats · The eval ledger