{"version":"2.1.268","anchor":"new-verification-required-error-classification-for-api-err","canonical_anchor":"new-verification-required-error-classification-for-api-err","heading":"New 'verification_required' error classification for API errors","tier":"notice","area":"Errors","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/new-verification-required-error-classification-for-api-err","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### New 'verification_required' error classification for API errors\n\nAPI errors can now be classified specifically as 'verification_required'\n\n**What**\n\nClaude Code's classification of errors coming back from the Anthropic API now includes a distinct `verification_required` category. It is checked before the existing `repeated_529` check, and sits alongside other existing categories like `rate_limit`, `capacity_off_switch`, and `prompt_too_long`.\n\n**Why**\n\nGiving this kind of error its own category lets Claude Code (and its error handling and messaging) respond to a verification requirement differently than to rate limits or capacity issues, rather than lumping it in with other error types.\n\n- Area: Errors\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}