One-time corpus cost by provider
Same corpus, every embedding model ranked cheapest first.
| Model | $/1M tokens | Dims | Corpus cost |
|---|
Embedding the corpus is the cheap part
The first instinct is to fear the cost of embedding a big knowledge base. Relax: modern embedding models are extraordinarily cheap per token — often two to thirteen cents per million tokens. Embedding 100,000 chunks of 500 tokens is 50 million tokens, which lands somewhere between $1 and $7 as a one-time cost on most providers. For typical corpora the one-time embed is a rounding error. The costs that actually add up live somewhere else, and they're easy to miss when you're estimating.
The two costs people forget
First, every query gets embedded too. A search product embedding 500,000 queries a month is paying a small recurring fee that, over a year, can quietly exceed the one-time corpus cost. Second, changing your embedding model or chunking re-embeds everything — switch from a small model to a large one, or re-chunk for better retrieval, and you pay the full corpus cost again. Teams iterating on retrieval quality re-embed several times before they're happy. Set your expected re-embeds per year above to see what that iteration really costs.
Storage is the bill that never stops
Embeddings are vectors, and storing millions of them in a managed vector database — Pinecone, Qdrant Cloud, Weaviate — is usually the largest ongoing line, dwarfing the embedding API itself. Higher-dimension models (1536, 3072) cost more to store and search than compact ones, so the cheapest embedding model per token isn't automatically the cheapest system. Price the storage and query side on the vector database cost calculator, then put the whole pipeline together on the RAG cost calculator.
Related tools & guides
Vector database cost calculator · RAG cost calculator · Fine-tuning cost calculator · LLM token cost calculator · All AI APIs