[FEATURE]: Add support for embedding models in OpenRouter #1359
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 of the changes
Adds support for OpenRouter embedding models
LlmApiType::OpenRoutermodule to accept the same parameters as Gemini/OpenAI models (task_typeandoutput_dimensionto allow embedding generation)No behavior changes for existing OpenRouter functionality; I only extended the existing embedding factory to route OpenRouter through the same embedding client used for OpenAI.
Motivation and context
OpenRouter now supports a few embedding models (type in "embedding" into the search box here. Users who are using OpenRouter LLMs for generative tasks can also use embedding models to generate embeddings in a CocoIndex flow, by selecting the appropriate model from the list of supported models in OpenRouter.
Note if it's a breaking change
How I tested
I built the library from source and ran the following code to generate embeddings in LanceDB (note the update to the
text_to_embeddingflow transform, where OpenRouter is called instead ofsentence-transformers). The flow runs through to completion and the embeddings are persisted to LanceDB 😄.