Fix KeyError: 'cost_usd' for Max subscription users #14
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This fix addresses issue anthropics#2 where Max subscription users encounter a KeyError when the API response doesn't include the 'cost_usd' field. Changes: - Modified ResultMessage dataclass to make cost_usd and total_cost_usd optional (float | None) - Updated client.py to use .get() with None default for cost-related fields - Maintains backward compatibility for users with cost data This ensures the SDK works for all subscription types, including Max subscriptions that don't have access to cost information. By: Unclecode <https://github.com/unclecode>
arun-pathiban-ddog
approved these changes
Jun 17, 2025
Collaborator
|
thank you @unclecode . Closing this PR as this issue is fixed with latest release |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes issue #2 where Max subscription users encounter a
KeyErrorwhen the API response doesn't include thecost_usdfield.Problem
Users with Max subscriptions were getting the following error:
This occurs because the SDK was expecting
cost_usdto always be present in the response, but Max subscription responses don't include cost information.Solution
ResultMessagedataclass to makecost_usdandtotal_cost_usdoptional (float | None)client.pyto use.get()method withNonedefault for cost-related fieldsTesting
Fixes #2