{"version":"2.1.246","anchor":"per-model-usage-says-which-price-table-produced-the-cost","canonical_anchor":"per-model-usage-says-which-price-table-produced-the-cost","heading":"Per-model usage says which price table produced the cost","tier":"notice","area":"Cost Tracking","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/per-model-usage-says-which-price-table-produced-the-cost","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Per-model usage says which price table produced the cost\n\nUsage records now say whether cost came from built-in prices, your org's rates, or a guess.\n\n**What**\n\nModel usage records gained `costBasis`, one of `list`, `managed` or `unknown`: Claude Code's built-in list prices, your organisation's managed-settings `modelPricing` rates or multiplier, or neither. When it is `unknown`, the reported `costUSD` is a guess based on the default model's rate.\n\n**Details**\n\n- Overwritten per request, so it reflects the most recent pricing decision for that model.\n- Absent until this process has priced at least one request for the model; consumers are told to treat absence as `list`.\n\n**Evidence**\n\n`costBasis`\n\n- Area: Cost Tracking\n- Names: `modelPricing`, `costBasis`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}