Add cost_dollars field to AnswerResponse and StreamAnswerResponse #135
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.
Add cost_dollars field to AnswerResponse and StreamAnswerResponse
Summary
Fixes #134 - The API returns
costDollarsin answer responses, but the SDK was not exposing this field.This PR adds the
cost_dollarsfield to:AnswerResponsedataclassStreamChunkdataclass (for streaming responses)The implementation follows the existing pattern used by
SearchResponsefor handlingcost_dollars, reusing the existingparse_cost_dollars()helper function.Review & Testing Checklist for Human
/answerendpoint actually returnscostDollarswith the expected structure (total, search, contents breakdown). TheCostDollarstype was designed for search responses - verify it matches answer responses.costDollarsis included in streaming chunks (typically the final chunk). I couldn't test this against the live API.Notes
SearchResponsehandlescost_dollars