{"version":"2.1.273","anchor":"new-structured-usage-response-schema-explicitly-marked-exp","canonical_anchor":"new-structured-usage-response-schema-explicitly-marked-exp","heading":"New structured \/usage response schema, explicitly marked experimental","tier":"soon","area":"Usage","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-structured-usage-response-schema-explicitly-marked-exp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### New structured \/usage response schema, explicitly marked experimental\n\nThe \/usage command gains a formally defined, still-experimental structured data schema\n\n**What**\n\nThe data behind the `\/usage` command (which shows session cost, plan usage limits, and activity stats) now has a formally defined structure covering:\n\n- session cost, duration, and lines-of-code totals\n\n- rate-limit rows, each with kind, group, percent used, reset time, scope, severity, and whether it's currently active, exactly as sent by the server\n\n- extra-usage (overage) spend details: whether it's enabled, the monthly limit, credits used, utilization, and currency\n\nThis is explicitly marked as experimental, meaning the shape may still change.\n\n**Why**\n\nA well-defined structure for usage data makes it easier for tools built on top of Claude Code, such as the SDK, to reliably read cost and rate-limit information, though it isn't finalized yet.\n\n- Area: Usage\n- Names: `\/usage`\n- Tier: Nothing to try yet\n- Useful: 4\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}