Gemini Embedding vs Jina Embeddings and Reranker

Gemini Embedding

Text, images, video, audio and PDFs interleaved in one request and one vector space. $0.20 per million text tokens, against $0.02 for OpenAI's small model.

Jina Embeddings and Reranker

jina-reranker-v3.5 (20 July 2026) with a 131,072-token window and no document cap. No price per token in any currency on the public pages.

Gemini Embedding

1. Don't send task_type to gemini-embedding-2. Prefix the text instead, task: search result | query: ... for queries and title: ... | text: ... for documents
2. Ask for output_dimensionality 768 unless you need 3072. Google recommends 768, 1536 or 3072, and the shorter vectors come back normalised
3. Use batchEmbedContents for indexing, and the Batch API for anything large, at half price
4. Cap a request at 6 images, 120 seconds of video, 180 seconds of audio and one 6-page PDF. Split longer media first
5. Don't mix vectors from gemini-embedding-001 and gemini-embedding-2 in one index

Jina Embeddings and Reranker

1. Send the whole candidate set to rerank in one call. The 131K window on v3.5 fits hundreds of chunks
2. On a 429, back off exponentially. Limits count per key when a key is sent, per IP otherwise
3. Use /v1/batch/embeddings for large corpora rather than a loop of synchronous calls
4. Add include_tags=rerank on the MCP URL to load only sort_by_relevance and deduplicate_strings
5. Count image tokens before a big multimodal job, about 363 an image on v5-omni