{"version":"2.1.285","anchor":"api-usage-carries-fallback-credit","canonical_anchor":"api-usage-carries-fallback-credit","heading":"Usage records gain a fallback_credit field","tier":"internal","area":"Usage","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/api-usage-carries-fallback-credit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Usage records gain a fallback_credit field\n\nAPI usage records now carry an optional fallback_credit field, which reports the outcome of a fallback-credit token a request presented\n\n**Unclear.** It is not clear how the fallback_credit value is used.\n\n**What**\n\nThe usage information attached to each API response, which records things like how many tokens a request used, now has a `fallback_credit` field.\n\n- `fallback_credit` is optional in the usage schema. It is described as the outcome of a fallback-credit token the request presented, or null.\n\n- It defaults to null and is carried through when usage from several requests is combined.\n\n**Why**\n\nThis is a data change that most people will not see directly. If you read the usage data Claude Code records or reports, expect a new `fallback_credit` field. It will be null unless a request presented a fallback-credit token.\n\n- Area: Usage\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}