LinklbeeLLM API COST DIAGNOSTIC

Linklbee LLM API Cost Diagnostic Report

scanner 1.4.13 · 1 file · 한국어: --lang ko[synthetic] example log
Cache hit rate

0.0% (synthetic log example)

The share of input tokens read from the cache (322 calls, the vendor's usage) · 0.0% on calls over the minimum. Details in 7-7.
Estimated savings for this log — of the bill

17.2% ~ 50.9% (synthetic log example)

Section 4 — ranges Linklbee measured on other public documents, applied to this log's reducible calls. Not a saving measured on this log.
17.2%50.9%0%100%
3
additional costs identified
  • 7-2 the same request resent shortly after
  • 7-3 answers cut off at the length limit
  • 7-4 request prefix serialized inconsistently
3
additional savings opportunities
  • 7-5 prompts shorter than the cache minimum
  • 7-8 prefix shared between calls
  • 7-9 calls that could use OpenAI Flex
0
more data required

Summary

The amounts shown are calculated by the diagnostic's rules. Actual savings are confirmed by measurement after integration.

Where to start

The 3 items found in section 2 with the largest amounts, of 6. Each item's numbers and method are in section 2, under the same code.

1. What was read

2. Checklist — what is leaking, what additional savings opportunities

Additional costs identified — money going out

Additional savings opportunities — cheaper ways, even with nothing wrong

The results in this section are based on the data provided and the calculation conditions shown.

3. Reducible share — the conclusion

Span (how many versions back the previous answer is taken from) — share of paired output at 0.99+ / under 0.78 / 0.85-0.99:

Before measuring, answers identical to the previous one were folded (repeats: 0 pairs, 0.0% of span-1 paired output), and answers that went back to an earlier version were left out (reverts: 0 pairs, 0.0%). Neither needs a call at any span, so neither counts toward the span's effect.

spananswer pairs>=0.99<0.780.85-0.99
113823.4%7.0%69.6%
21084.7%5.8%89.5%
3780.0%3.9%96.1%
4480.0%0.0%97.8%
60———
80———

Span chosen per length tier (answer-token edges [532.0, 558.0], this log's tertiles): 1*, 1*, 1*. A tier with fewer than 100 answer pairs keeps span 1. A span of 2 or more is chosen only where it beats span 1 on the same answers, including at the 2.5th percentile of a per-document resample.

4. Estimated savings (expected range)

This section covers only calls that can be answered by rewriting the changed parts. On a log whose documents do not resemble each other, 0 is the expected result; see section 2.

This is not a saving measured on this log. The ranges Linklbee measured on other public documents (below) are applied to this log's reducible calls. Everything else counts as 0.

Ranges Linklbee measured (three public document sets (product copy, drug label revisions, statute revisions), real calls, failed-edit re-calls included (not for product copy: no call records), 2026-10):

5. Answer pairs by similarity and length

138 answer pairs from 170 documents. Each pair compares an answer with the previous answer for the same document. Similarity here is measured with the answer known. How documents were found: 308 calls by the document key in the log · 0 calls grouped by the scanner (0 pairs) · 0 skipped for an identical timestamp.

similarity \ length<200200-500500-20002000+
>=0.95——100 · 62.4%—
0.78-0.95——20 · 13.1%—
0.60-0.78—2 · 0.7%——
<0.60—16 · 5.0%——

Each cell: answer pairs · share of all output tokens. Bold = reducible (similarity 0.78+ and answer 200+ tokens). Pair similarity, token-weighted 0.934, median 0.975.

6. Answering without a call

7. How much of the bill is output

8. Items that came out 0 — why, and what to look at next

One line per item: (a) the reason, counted on this log · (b) what would change it, or what to look at instead. Every figure is either counted on this log or a line Linklbee set (its name in brackets).

These items came out at 0 on this analysis. That is not an analysis error; each line above gives the reason and what more would be needed.

Send this report to bee@linklbee.com and we will look deeper, free of charge. The report holds no prompt or answer text — only numbers, patterns and model names. No need to send the log.

took 2.1s

Review optimization opportunities in your report

Share the diagnostic summary for a free review of cost patterns, applicable improvements, and suggested priorities.

The scanner does not transmit data automatically. This action prepares a diagnostic summary in your email app; you decide whether to send it.

Review information to share

The summary excludes prompt and response content, document names, and API keys. Review the information below before sharing.