{"version":"2.1.311","anchor":"per-lifetime-cache-write-token-fields-in-usage","canonical_anchor":"per-lifetime-cache-write-token-fields-in-usage","heading":"Usage now splits cache writes into 5-minute and 1-hour counts","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/per-lifetime-cache-write-token-fields-in-usage","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Usage now splits cache writes into 5-minute and 1-hour counts\n\nUsage records add `cacheCreationEphemeral5mInputTokens` and `cacheCreationEphemeral1hInputTokens`, and 1-hour cache writes are costed at the 1-hour rate\n\n**What**\n\nClaude Code can cache (store and reuse) parts of a conversation so it does not have to send them again. A cache entry can last 5 minutes or 1 hour. Usage records used to give only one total for tokens written to the cache, `cacheCreationInputTokens`. They now also carry two optional counts:\n\n- `cacheCreationEphemeral5mInputTokens`, for tokens written to a 5-minute cache.\n\n- `cacheCreationEphemeral1hInputTokens`, for tokens written to a 1-hour cache.\n\n`costUSD`, the cost estimate, now prices 1-hour cache writes at the 1-hour rate when the price table has one.\n\n**Why**\n\nThe two cache lengths cost different amounts, so splitting them gives a more accurate cost breakdown and estimate.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}