Loading the catalogue…
Loading the catalogue…
OpenAI's cost-efficient third-generation text embedding model for semantic search and retrieval, producing configurable 1,536-dimension vectors.
Overview. text-embedding-3-small is OpenAI's third-generation text embedding model, released in January 2024 alongside the larger text-embedding-3-large. It converts text into 1,536-dimension vectors by default (with configurable dimension truncation for smaller storage footprints) and is available exclusively through OpenAI's API — there is no open-weight release. Developers reach for it when they need a compact, general-purpose text encoder for semantic search, clustering, or retrieval-augmented generation pipelines.
Key strengths. As a pure text-to-vector encoder, it performs a single forward pass per input rather than an autoregressive decode loop, which supports low end-to-end latency in real-time retrieval pipelines. It supports input sequences up to roughly 8,191 tokens using the cl100k_base tokenizer, and its configurable output dimensionality lets teams trade vector size against storage and search-index cost without re-embedding from scratch. No independent quality benchmarks (retrieval accuracy, MTEB-style scores) are available in current research, so strengths here are architectural rather than benchmark-verified.
When to use it. Use this model for semantic search, document clustering, deduplication, or as the retrieval layer in a RAG pipeline where you need fast, single-pass text encoding rather than generative output. It's a reasonable default when you want a smaller, faster-to-produce embedding than OpenAI's larger third-generation sibling and don't need the absolute highest retrieval fidelity available in that family. It is not a generative or chat model — it has no system-prompt, tool-calling, or streaming support, so it should sit purely in an embedding/indexing stage of an application.
Limitations. OpenAI has not disclosed the model's architecture, parameter count, or training-data cutoff, and there is no public weights repository — it is closed and API-only. The 8,191-token input cap is modest compared to modern generative context windows, and output is a fixed-dimension vector rather than text, so it cannot be used for any generative task.
Sovereignty note. OpenAI is a US-based creator with confirmed CLOUD Act exposure, and text-embedding-3-small has no self-hosted Sovereign alternative — though eligible API customers can opt into EU data residency, teams routing regulated or sensitive data should still treat this as a non-Sovereign, US-jurisdiction endpoint given OpenAI's CLOUD Act exposure.
| Inference Provider | Sovereignty | Runs in | Price | Status | Pin |
|---|---|---|---|---|---|
| L0 | €0.02 per 1M input tokens | Online |
9 use cases classified by the curator. The note says why.
Purpose-built embedding model producing 1,536-dimension vectors for semantic search; this is the core designed use case for text-embedding-3-small.
Embedding vectors are commonly used as features for downstream classification pipelines, though this requires additional tooling since the model itself has no classification head or instruction-following flagged.
Embedding similarity can support reranking pipelines, but the small variant trades capacity for cost versus the large tier, making it a budget-tier reranking signal rather than a top-tier one.
Configurable 1,536-dim embeddings support similarity-based tagging workflows, a common secondary use for retrieval embeddings.
No generation capability is flagged for this model; it produces embeddings only and cannot synthesize answers over retrieved documents.
Embedding-only model with no generative capability — unsuitable for direct document Q&A, though it could feed a retrieval layer for a separate generator.
No generative or extraction capability is flagged; this is a pure embedding model unsuited to producing structured extraction output directly.
This is an embedding-only model with no generative or instruction-following capabilities flagged, so it cannot itself rewrite queries — only support downstream retrieval via vector similarity.
Embedding-only architecture with no capabilities flagged for generation or structured output — not designed for extraction tasks.
Sourced numbers, not our own evaluations. Percentiles are against the embedding models on Stav.
curl https://api.stav.ai/v1/embeddings \
-H "Authorization: Bearer $STAV_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "openai/text-embedding-3-small",
"input": ["Hello, world"]
}'→ X-Stav-Request-Id · X-Stav-Model · X-Stav-Provider → X-Stav-Sovereignty-Level — the rung the request was served at