Embed v1 0.6b
import { embed } from 'ai';
const result = await embed({ model: 'perplexity/pplx-embed-v1-0.6b', value: 'Sunny day at the beach',})Providers
Route requests across multiple providers. Copy a provider slug to set your preference. Visit the docs for more info. Using a provider means you agree to their terms, listed under Legal.
More models by Perplexity
| Model |
|---|
| 32K | $0.03/M | — |  | 02/26/2026 | |||||||||
| 127K | 2.1s | 221tps | $1/M | $1/M | $5/K*+2 more | | 02/19/2025 | ||||||
| 200K | 1.2s | $3/M | $15/M | $6/K*+2 more | | 02/19/2025 | |||||||
| 127K | 3.0s | 132tps | $2/M | $8/M | $6/K*+2 more | | 02/19/2025 |
About Embed v1 0.6b
Embed v1 0.6b is the smaller of Perplexity's two standard embedding models, released February 26, 2026. It targets high-volume embedding, where per-token cost rather than the last point of recall sets the ceiling on how much you can index. Like the 4B tier, it uses bidirectional attention with mean pooling and returns unnormalized INT8 vectors by default.
The size difference shows up in two places. Embed v1 0.6b returns 1024-dimensional vectors against 2560 for pplx-embed-v1-4b, so each vector takes less room in the index. Binary quantization is also less forgiving at this scale: Perplexity measures a 2 to 4 percentage point quality drop from binary output at 0.6B, against under 1.6 points at 4B. Test binary output on your own queries before you binarize a large index.
Retrieval quality holds up better than the parameter count suggests. On Perplexity's PPLXQuery2Query benchmark over a 2.4 million document corpus, Embed v1 0.6b reaches 71.1% Recall@10, against 61.8% for BGE-M3 and 55.1% for Qwen3-Embedding-0.6B. On the BERGEN end-to-end retrieval-augmented generation benchmark, Embed v1 0.6b outperforms the larger Qwen3-Embedding-4B on three of five question-answering tasks. Perplexity also reports that Embed v1 0.6b outperforms its Qwen3 counterpart at the same parameter scale on MTEB(Multilingual, v2).
What To Consider When Choosing a Provider
- Configuration: Embed v1 0.6b returns unnormalized embeddings. Compare INT8 vectors with cosine similarity and binary vectors with Hamming distance. If your vector database only supports inner product, convert to float32 and L2-normalize before storing.
- Configuration: Binary quantization costs more quality here than on the 4B tier, 2 to 4 percentage points against under 1.6. Start with INT8 at the full 1024 dimensions and compress only when storage forces the issue.
- Configuration: Perplexity recommends embedding documents and queries with the same model. Mixing Embed v1 0.6b with
pplx-embed-v1-4bacross the two sides makes similarity scores unreliable, and moving between the two later means re-embedding the corpus. - Zero Data Retention: AI Gateway does not currently support Zero Data Retention for this model. See the documentation for models that support ZDR.
- Authentication: AI Gateway authenticates requests using an API key or OIDC token. You do not need to manage provider credentials directly.
When to Use Embed v1 0.6b
Best for
- High-Volume Embedding: Per-token cost sets the practical ceiling on corpus size
- Compact Vector Indices: 1024-dimensional output keeps the index small
- Retrieval Prototyping: Iterate on chunking and queries before locking a dimension count
- Multilingual Semantic Search: Evaluated on MTEB(Multilingual, v2) alongside the 4B tier
- Prompt-Free Integration: No instruction prefix can drift between indexing and query time
Consider alternatives when
- Accuracy Is Binding:
pplx-embed-v1-4breturns 2560-dimensional vectors for higher recall - Large Binary Indices: Binary quantization costs more quality at this parameter scale
- Code-Only Corpora:
voyage-code-3is purpose-built for source code retrieval - Generated Text Required: This model returns vectors only, not completions
Conclusion
Embed v1 0.6b keeps embedding cost low without dropping to a weaker generation. It matches the 4B tier on integration surface: no instruction prefix, native INT8 output, and a context window of 32K tokens. Start here when your corpus is large, then move to pplx-embed-v1-4b if recall testing on your own queries shows you need it.