# How to track LLM cost by prompt version > Without a version on every call, a prompt edit and a price change look identical in the total. Tagging the version is what separates them. URL: https://getculpa.com/track-llm-cost-by-prompt-version Last reviewed: 2026-08-03 Rates effective: 2026-07-02 ## Answer To track LLM cost by prompt version you record which version produced each call, then price the calls and compare versions on cost per call rather than on total spend. Culpa, a local-first LLM cost, margin, and forecast ledger, tags every call with its version and prices it from a versioned price book, so a prompt change and a rate change stay separable. ## Why this happens A prompt edit is a deploy that changes your unit cost, and almost nobody treats it as one. Add two sentences of instruction to a system prompt and every call from that moment carries them, so a change that took a minute to write raises cost for as long as it ships. The reason it goes unnoticed is that the total moves for several reasons at once. Traffic grew, a provider changed a rate, someone switched a model, and someone edited a prompt, and a single monthly number can't separate those. Tagging each call with the version it came from separates them completely, because cost per call under version 4 against version 3 holds traffic constant by construction. Without that tag, the honest answer to why the bill moved is that nobody knows, and the usual response is to blame volume. ## What this usually looks like - Cost per call rose and traffic didn't, and nobody can name the change. - A prompt was edited last month and no record connects it to the bill. - You compare prompt versions on quality and never on cost. - A rollback fixed spend and nobody can prove which version was responsible. - Your prompts are versioned in one system and your spend lives in another. ## Common mistakes - Comparing prompt versions on total spend. Why it hurts: Totals move with traffic. Two versions running at different volumes can't be compared that way. Do instead: Compare cost per call, which holds volume constant by construction. - Treating a prompt edit as content rather than a deploy. Why it hurts: It changes unit economics on every call afterwards and usually ships without review. Do instead: Version prompts, tag calls with the version, and price the change before it goes out. - Tagging only the calls your own code makes. Why it hurts: Framework retries and sub-calls run the same prompt and land untagged, so the version's real cost is understated. Do instead: Confirm on a live trace that every call carrying that prompt also carries the version. - Assuming a longer prompt costs proportionally more. Why it hurts: It depends where the tokens land. Input is usually several times cheaper than output. Do instead: Price the actual input and output split rather than reasoning from prompt length. ## Self-check - Name the current version of your highest-volume prompt, and when it last changed. - Find the cost per call of the version before it. - Add up the tokens your system prompt contributes to a single call. - Multiply that by last month's call count and decide whether the wording was worth it. ## What two sentences cost at volume A modelled system prompt gains 180 tokens of extra instruction, which is roughly two careful sentences with an example. Priced on Claude Haiku 4.5 at a real input rate of $1.00 per million from the price book, effective 2026-07-02, across a modelled 4 million calls a month. Nothing else about the workload changes. 180 extra input tokens x 4,000,000 calls = 720,000,000 extra input tokens a month 720M tokens / 1,000,000 = 720 million-token units 720 x $1.00 = $720.00 a month, from the prompt edit alone cost per call rises by $0.00018, which is invisible in any single call The per-call number is too small to notice and the monthly number is a hire. That gap is the entire argument for versioning: the change is undetectable at the granularity people look at, and material at the granularity finance uses. ## Cost figures Every figure carries its confidence and its source. No figure on this page is provider-reported. - $720.00 per month, modelled cost of adding 180 input tokens to a system prompt at 4M calls a month [calculated] Source: 180 tokens x 4,000,000 calls = 720,000,000 input tokens, at the real Claude Haiku 4.5 input rate of $1.00 per million from the price book effective 2026-07-02, giving $720.00. The token increment and the call volume are modelled. The rate is real. - $0.00018, the same change expressed per call, where it disappears into the noise [calculated] Source: 180 tokens at $1.00 per million = $0.00018 per call, from the same real rate. Shown beside the monthly figure because the pair is the finding: the same change is invisible at one granularity and material at another. ## FAQ Q: How do I compare the cost of two prompt versions? A: On cost per call, never on total spend. Totals move with traffic, so two versions running at different volumes can't be compared directly. Cost per call holds volume constant, which is what makes the difference attributable to the prompt. Q: How much can a small prompt edit actually cost? A: At 4 million calls a month, 180 extra input tokens is 720 million extra tokens, which is $720.00 a month at a $1.00 per million input rate. The per-call increase is $0.00018 and invisible, which is exactly why it needs measuring rather than noticing. Q: What if my prompts are versioned in another tool? A: That's common and it's only half the problem. The version has to travel on the call and land beside the token counts, otherwise the two systems can't be joined afterwards. Tag at capture, not at analysis. Q: Can I separate a prompt change from a provider price change? A: Only if the version is on the call and rates carry effective dates. With both, a past month recomputes at the rate in force when it ran, so a rate rise and a prompt edit stay two distinct movements rather than one confusing total. ## Sources - Anthropic pricing: https://platform.claude.com/docs/en/docs/about-claude/pricing Run the free Cost Leak Scan: https://app.getculpa.com/scan?source=pseo&slug=track-llm-cost-by-prompt-version&cluster=attribution Machine-readable index of every guide: https://getculpa.com/api/pages Human-readable index of every guide: https://getculpa.com/guides Site overview: https://app.getculpa.com/llms.txt Privacy: Culpa runs on your infrastructure. Your prompts and responses never leave it. Culpa counts calls to run your plan, and it fails open, so if it ever breaks your app keeps running.