{"version":"2.1.301","anchor":"usage-api-schema-accepts-periods-and-tolerates-a-changed-lim","canonical_anchor":"usage-api-schema-accepts-periods-and-tolerates-a-changed-lim","heading":"Usage data can now include time periods","tier":"soon","area":"Usage & Limits","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/usage-api-schema-accepts-periods-and-tolerates-a-changed-lim","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Usage data can now include time periods\n\nClaude Code now accepts an optional list of time periods, each with a start and end, in the usage data it receives\n\n**What**\n\nThe usage data Claude Code receives about your account can now include an optional list of time periods, each with a start and an end time. Nothing visible uses it yet.\n\n**Why**\n\nThis looks like preparation for showing usage by period.\n\n- Area: Usage & Limits\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}