TL;DR: every number below came out of my own terminal on 2026-09-18, three bl text chat calls, total cost under two US cents of compute at marketplace unit prices (labeled estimate, usage fields not captured).
The gap nobody prices
One model telling you "no bugs found" is worth almost nothing. You have no idea whether it looked or just agreed with itself. Two models that never talked to each other, naming the same three lines independently, is a different kind of evidence entirely. That second kind used to cost you a colleague's afternoon. It now costs a few cents.
The setup
A snippet with three real defects planted: skipped first element, divide-by-zero on empty input, and a discount function returning the discount amount instead of the discounted price. I did not tell the models what to look for.
The three commands
bl text chat --model qwen3.8-flash --timeout 120 --message "<code> List only real problems, one per line, no explanation"
bl text chat --model kimi-k3 --timeout 150 --message "<code> List only real problems, one per line, no explanation"
bl text chat --model qwen3.8-max --timeout 150 --message "<code + both reviews> False positives or misses? Which fix first? One line of fix code"
Reviewer A took 98 seconds and returned three lines. Reviewer B took 18 seconds and returned the same three lines plus a fix for the third. The judge took 104 seconds, confirmed neither review had false positives or misses, picked the divide-by-zero as first-to-fix, and produced return sum(prices) / len(prices) if prices else 0. I checked that line by hand: it fixes both the skipped element and the division by zero.
Why agreement beats confidence
The judge's most useful output was not the verdict. It was the ordering. "Fix this one first" is exactly the judgment that consumes human reviewer time; finding the lines is the cheap part. Getting that ordering from a third model that read both opinions is a workflow, not a demo.
Two boundaries, stated plainly. This is a review workflow, not a safety mechanism; a human still reads the verdict. And review-style prompts make models think for one to two minutes, so keep --timeout in the command or a non-streamed long-thinking request will look hung. I lost ten minutes to that one before I understood it.
Run it, then argue with it
The CLI is on the install page; from the second call you need an API key from the console, and new accounts carry free quota. The platform overview is here if you want the wider picture first.
If your roundtable catches something mine missed, or your judge overrules two agreeing reviewers, I want that case. Three opinions are only worth what the fourth one finds.
Top comments (0)