← Back to all posts

Embedding Model

On this page

Purpose

Embedding Model configures an embeddings client for semantic search and retrieval. It does not receive source text directly or return raw vectors.

When to use it

  • Configure embeddings for a ChromaDB retrieval workflow.
  • Choose Arkus or OpenAI embeddings for a vector store.
  • Tune provider batching and retry behavior.

Required setup

Arkus is the default provider and uses the text-embedding-3-small deployment. It does not show an API key or base URL. OpenAI requires an OpenAI API key.

How to use it

  1. Add Embedding Model and select a provider and model.
  2. Connect Embedding Model to ChromaDB.
  3. Connect prepared Data to the vector store for ingestion.
  4. Run the vector store search path.

Configuration

SettingWhat it controlsRecommended starting point
Model ProviderSelects Arkus or OpenAI.Start with Arkus.
Model NameSelects the provider model or Arkus deployment.Keep the default Arkus deployment unless the flow needs another model.
OpenAI API KeyAuthenticates OpenAI embeddings.Use a saved Credential.
DimensionsRequests a compatible vector size for supported models.Leave blank unless the vector store requires a size.
Chunk SizeNumber of text chunks in one embedding request.Leave at 36.
Max RetriesProvider retry count.Leave at 3.

Expected result

The component returns a configured Embeddings client. ChromaDB uses it to create and search vectors. Chunk Size batches provider requests. It does not split source documents, so use a preparation component before vector-store ingestion.

Reference details

Request Timeout, Show Progress Bar, Model Kwargs, and Dimensions are provider options. OpenAI validates its client with a small test embedding during build. Arkus does not make that validation call.

Provider credentials and credits

Arkus embedding calls use Arkus credits based on input tokens. OpenAI uses the selected OpenAI account and bypasses Arkus embedding metering. A deployed OpenAI key must be a saved Credential reference where credential-bearing deployment is enabled.

← Back to all posts