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
Currently, the Vercel AI SDK only supports text embedding models. We would like to request the addition of support for creating embeddings for images as well.
As image-based machine learning and multi-modal AI applications become more common, the ability to generate embeddings for images would greatly enhance the SDK’s capabilities. This feature would allow developers to leverage image similarity, classification, and other AI-driven tasks directly within the Vercel ecosystem.
Use Cases
Image Similarity: Create vector embeddings from images and compare them for similarity.
Multi-modal Applications: Combine text and image embeddings for more comprehensive AI models (e.g., image captioning, visual question answering).
Image Classification: Use embeddings for classification tasks where images need to be mapped to specific categories.
Additional context
We believe this feature would provide significant value and open up new possibilities for developers using the Vercel AI SDK. Looking forward to seeing this feature in a future release!
The text was updated successfully, but these errors were encountered:
Feature Description
Currently, the Vercel AI SDK only supports text embedding models. We would like to request the addition of support for creating embeddings for images as well.
As image-based machine learning and multi-modal AI applications become more common, the ability to generate embeddings for images would greatly enhance the SDK’s capabilities. This feature would allow developers to leverage image similarity, classification, and other AI-driven tasks directly within the Vercel ecosystem.
Use Cases
Additional context
We believe this feature would provide significant value and open up new possibilities for developers using the Vercel AI SDK. Looking forward to seeing this feature in a future release!
The text was updated successfully, but these errors were encountered: