You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suspect langsmith is counting the image passed as base64 as it was a normal string instead of being tread as an image for the vision api. A call that actually costed me 0.03 is being reported as $2.2. This can be also observed by the token count that takes in consideration the full base64 encoded string (which is not wrong per se). Display of the submitted image in the prompt is working as expected so thumbs up for that :)
Suggestion:
The cost should be calculated using the pricing model of the gpt-4-vision-preview and not the standard model.
The text was updated successfully, but these errors were encountered:
I'm seeing a similar issue with Gemini Pro Vision, no cost data is displayed, but the number of tokens for a request with an image are in the millions. Hoping the fix mentioned above covers this as well?
Issue you'd like to raise.
Hello, I'm running the following configuration:
I suspect langsmith is counting the image passed as base64 as it was a normal string instead of being tread as an image for the vision api. A call that actually costed me 0.03 is being reported as $2.2. This can be also observed by the token count that takes in consideration the full base64 encoded string (which is not wrong per se). Display of the submitted image in the prompt is working as expected so thumbs up for that :)
Suggestion:
The cost should be calculated using the pricing model of the gpt-4-vision-preview and not the standard model.
The text was updated successfully, but these errors were encountered: