Results
Selective regeneration: cost and quality compared
We called every item twice with the same model: through Linklbee and as a full rewrite. Quality is compared with the version actually published next. Measured on public document data. Your own results are confirmed by a scan of your logs and a pilot.
| Dataset (public) | Calls | Output tokens | Cost |
Quality · Linklbee | Quality · full rewrite | Quality · last version as is |
| Korea MFDS drug-label revisions | 45 | −75.1% | −57.0% | 0.972 | 0.9628 | 0.9593 |
| Korean statute amendments | 317 | −57.1% | −38.2% | 0.9777 | 0.9811 | 0.9385 |
The −38.2% we publish includes 0% from reusing a previous answer without a call. Every edit call was actually made, and the API cost of reprocessing after a failed edit is included.
“Four in ten” (the share of answers that change when a call is skipped) was measured directly with 78 paid calls (2026-10-18).
In the statute revision test, 🧪 309 of 317 items scored higher on quality than using the previous version unchanged. The statute row’s output and cost include retrying the 18 items whose edits failed to apply as full rewrites, as the product does (recomputed from the same call records). The MFDS row went through the product server as is, so the cost of its one real fallback is already inside. Cost savings are smaller than output savings because the attached draft adds input tokens; that increase is already subtracted. Statute and MFDS rows: reasoning off, for both control and treatment. Model claude-sonnet-5-5 for both, 2026-10-17 to 19.
ValueOutput-token savings and cost savings
Sample45 · 317 items
Compared withThe same items rewritten in full by the same model
Measured byCost is computed from the AI provider’s usage figures; quality is the token F1 against the real next version. The criteria were fixed before the experiment.
Run it yourselfThe scanner measures how much of your logs it can reduce