{"version":"2.1.293","anchor":"pricing-lookup-now-resolved-per-usage","canonical_anchor":"pricing-lookup-now-resolved-per-usage","heading":"Cost estimates now look up pricing for each usage record","tier":"notice","area":"Cost Tracking","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/pricing-lookup-now-resolved-per-usage","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Cost estimates now look up pricing for each usage record\n\nClaude Code now looks up a pricing entry from the model and the usage details before working out an estimated cost\n\n**Unclear.** Which kinds of usage get a different price is not known, so it is unclear whose cost estimates will change.\n\n**What**\n\nWhen Claude Code works out the estimated cost of a request, it now looks up which pricing entry applies, based on the model and the usage details of that request. Before, it applied the same fixed per-token rates every time.\n\n**Why**\n\nCost estimates can come out differently for some kinds of usage than they did before.\n\n- Area: Cost Tracking\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}