Loading the catalogue…
Loading the catalogue…
OpenAI's flagship closed-weight text embedding model, producing configurable-dimension vectors (up to 3,072-d) for search and retrieval workloads with an 8,191-token input window.
Overview. text-embedding-3-large is OpenAI's flagship text embedding model, released in January 2024. It converts text into dense vectors for search, clustering, and retrieval workloads, supporting configurable output dimensions up to 3,072 via Matryoshka Representation Learning, with an 8,191-token input window. Developers reach for it when they need a single, well-supported embedding endpoint for building retrieval-augmented pipelines or semantic search.
Key strengths. The model's dimension-flexibility lets teams trade vector size against storage and search cost without switching models, since a single embedding can be truncated to fewer dimensions while retaining representation quality. Its 8,191-token context window comfortably covers most document chunks, paragraphs, and multi-sentence passages in one call. As a closed-weight, API-only model, it benefits from OpenAI's ongoing maintenance rather than requiring self-hosting.
When to use it. Use this model when you need general-purpose text embeddings for semantic search, retrieval-augmented generation, clustering, deduplication, or recommendation systems, and want a single input-text endpoint rather than a chat interface. It's a good fit when input chunks stay under the 8,191-token limit and when you want the option to store lower-dimensional vectors for cheaper indexing without re-embedding from scratch.
Limitations. This is a non-generative, text-in/vector-out model: it has no chat interface, tool calling, streaming, or system-prompt support, so it cannot be used for generation or reasoning tasks. OpenAI has not disclosed the model's parameter count, architecture, or training-data cutoff, which limits transparency for teams that need that information for evaluation.
Sovereignty note. text-embedding-3-large is built by OpenAI, a US-based creator, so data sent to this endpoint is subject to US CLOUD Act exposure rather than EU-only Sovereign guarantees.
| Inference Provider | Sovereignty | Runs in | Price | Status | Pin |
|---|---|---|---|---|---|
| L0 | €0.12 per 1M input tokens | Online |
12 use cases classified by the curator. The note says why.
Purpose-built embedding model with configurable up-to-3,072-dim vectors and 8,191-token input window — this is the core designed use case for text-embedding-3-large.
High-dimensional embeddings support downstream classifiers (e.g. k-NN, linear probes) effectively, though the model itself performs no classification — it only supplies feature vectors.
Embedding similarity scores can drive reranking pipelines, but this is a general-purpose embedding model, not a dedicated cross-encoder reranker, so precision on hard reranking tasks will lag specialized rerankers.
Embedding-based similarity clustering can support automated tagging workflows, consistent with the model's stated clustering use case.
No tool-calling or agentic capabilities are flagged; this is a pure embedding model with no action-taking or code-generation function.
No generative capability flagged — this model cannot produce answer text, only retrieval vectors for a downstream generator.
No code-generation or completion capability is flagged for this embedding-only model.
Document Q&A requires natural-language answer generation, which is outside this embedding model's function.
No generative or extraction capability is flagged — this model produces vector representations only and cannot perform span-level entity extraction.
No vision capability is flagged for text-embedding-3-large — it is a text-only embedding model.
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-large",
"input": ["Hello, world"]
}'→ X-Stav-Request-Id · X-Stav-Model · X-Stav-Provider → X-Stav-Sovereignty-Level — the rung the request was served at