Equation 10 · Comparing Frontier Model Pricing Without Comparing Apples to Oranges
What does this equation mean?
Read the formula alongside the article passage below. Each part has a deeper page with its role in the equation, the supporting passage and nearby citations.
This equation states an equality: the expressions on both sides have the same value under the article’s assumptions. Read the equation part by part below; each part has a contextual explanation and a link to its mathematical background.
Read it piece by piece
Symbol C_i
is part of the quantity the equation computes from the expression on the right.
Symbol kappa_i
kapp is one of the signed contributions combined to compute the quantity on the left.
Symbol h_i
the fraction of input served from cache and the cache-read multiplier.
Symbol rho_i
all equal to each other and to 1 across every vendor in the comparison.
Symbol p^out_i
u is one of the signed contributions combined to compute the quantity on the left.
=
The expressions on both sides represent the same quantity under the stated assumptions.
See an illustrated explanation →subscript
The lower label selects a particular version, component, or indexed member of the quantity. For example, x₀ and xₜ can be values at different positions.
superscript
A raised number can be a power. When it is a label or bound, it selects a case or the upper limit of a sum; the formula’s structure distinguishes these uses.
See an illustrated explanation →How to interpret it
Read it with the definitions, units, and assumptions supplied by the article.
What the article says around this equation
Collecting every distinction above into one expression makes explicit what a bare price comparison assumes without saying so. For vendor i , let and be the published input and output rates; let be a tokenizer expansion factor, the number of tokens vendor i ’s own tokenizer needs to encode one fixed reference passage, normalised so = 1 for whichever vendor is used as the baseline; let be the fraction of input served from cache and the cache-read multiplier; and let be the ratio of total output tokens generated, visible answer plus hidden reasoning, to the visible answer alone. A workload’s realised cost per completed task…
Read the full surrounding passage
Collecting every distinction above into one expression makes explicit what a bare price comparison assumes without saying so. For vendor i , let and be the published input and output rates; let be a tokenizer expansion factor, the number of tokens vendor i ’s own tokenizer needs to encode one fixed reference passage, normalised so = 1 for whichever vendor is used as the baseline; let be the fraction of input served from cache and the cache-read multiplier; and let be the ratio of total output tokens generated, visible answer plus hidden reasoning, to the visible answer alone. A workload’s realised cost per completed task is then approximately . Reading and off a rate card and comparing them directly across vendors is equivalent to assuming , , and are all equal to each other and to 1 across every vendor in the comparison. This article has just shown that one of those three, , genuinely does converge close to 0.1 across all three companies’ published cards — the one term a naive comparison happens to get right by accident. The other two do not converge, are not published as clean multipliers by any vendor, and vary by content type and by task in ways that only measurement on the caller’s own workload can pin down. A price comparison that reports and alone has silently set = = 1 for every vendor, an assumption none of the sourcing above supports.
Sources cited in the article section
- [8] Comparison of AI Models across Intelligence, Performance, and Price ↗
- [7] LLM Inference Price Trends ↗
These citations give research context. Read each source to check which claims it supports.
Return to Comparing Frontier Model Pricing Without Comparing Apples to Oranges