feat(voyageai): expose token usage in rerank results #2
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR enhances the VoyageAIRerank functionality by exposing token usage information in the rerank results. Now, each returned Document in the rerank output includes a total_tokens field in its metadata, reflecting the number of tokens consumed during the reranking operation.
Details
The rerank result's Document.metadata now contains both relevance_score and total_tokens.
This allows downstream consumers to access token usage information for monitoring, analytics, or cost estimation purposes.
Unit tests have been updated to verify the presence and correctness of the total_tokens field in the rerank results.