claude-code - 💡(How to fix) Fix [BUG] API Error 400 persists after claiming $100 third-party usage credit [4 comments, 5 participants]

After Anthropic's billing change that separates third-party app usage from plan limits, one of my Claude Code instances returns a 400 error even after claiming 2. One instance works fine, the other returns the error below 3. Claimed the $100 credit as instructed in the error message 4. Restarted the failing instance — same error persists Error API Error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Third-party apps now draw from your extra usage, not your plan limits. We've

Error Messages/Logs

1. One instance works fine, the other returns the error below
2. Claimed the $100 credit as instructed in the error message
3. Restarted the failing instance — same error persists

TL;DR

Claiming the $100 credit may not be properly synced across all Claude Code instances, requiring a re-authentication or refresh of the instance configuration.

Guidance

• Verify that the $100 credit is correctly applied and visible in the account settings for the specific instance that's failing.
• Check if there are any instance-specific settings or configurations that might be overriding the credit application.
• Attempt to re-authenticate or refresh the configuration of the failing Claude Code instance to ensure it recognizes the updated credit status.
• If the issue persists, consider reaching out to Anthropic support for further assistance, as the problem might be related to their billing changes or API handling.

Example

No specific code example is applicable in this case, as the issue seems related to configuration and authentication rather than code implementation.

Notes

The exact cause of the discrepancy between the two instances is unclear, but it appears to be related to how the $100 credit is applied and recognized by each instance. This issue might be specific to the interaction between the Anthropic billing system and the Claude Code instances.

Recommendation

Apply workaround: Re-authenticate or refresh the configuration of the failing instance, as this might resolve the synchronization issue with the $100 credit application.