Skip to content

Voyage AI and Jina AI

The two hosted specialist retrieval providers: embeddings and reranking, no generation. Both serve native query/document input intents and a real reranker; they differ in task vocabulary, batch ceilings, and truncation behavior.

Setup

import anyinfer as ai

client = ai.Client([ai.ProviderSettings.of("voyage", api_key="env://VOYAGE_API_KEY")])

docs = client.embed(corpus, target="voyage:voyage-3.5", input_type="document")
query = client.embed([question], target="voyage:voyage-3.5", input_type="query")
ranked = client.rerank(question, candidates, target="voyage:rerank-2.5", top_n=5)

import anyinfer as ai

client = ai.Client([ai.ProviderSettings.of("jina", api_key="env://JINA_API_KEY")])

docs = client.embed(corpus, target="jina:jina-embeddings-v3", input_type="document")
query = client.embed([question], target="jina:jina-embeddings-v3", input_type="query")
ranked = client.rerank(question, candidates, target="jina:jina-reranker-v3", top_n=5)

Provider Differences

Voyage AI Jina AI
Input intents query and document only; classification/clustering have no wire value, are never sent, and the result carries a warning All four: query → retrieval.query, document → retrieval.passage, classification verbatim, clustering → separation (Jina's clustering-flavored task, recorded in the contract)
Embedding batches Batching engages at 1,000 inputs No documented ceiling: Jina batches internally, so no limit is invented; requests above the library's sanity ceilings refuse locally, and BatchPolicy.max_items_override applies an independently verified limit
Rerank documents 1,000 is a hard cap; the core refuses larger requests unless rerank_cross_batch opts into chunk-local rankings top_n is taken natively by the reranker
Truncation Defaults on server-side: over-length inputs are cut, not rejected. Disable per call with provider_options={"voyage": {"truncation": False}} —
Dimensionality — Matryoshka truncation via dimensions=; late_chunking via provider_options={"jina": {"late_chunking": True}}

Notes

Two behaviors are shared:

  • No model listing. Neither API has a listing endpoint, so client.models("voyage") and client.models("jina") return empty lists; the verified model set ships in each descriptor's capabilities.
  • Usage is total_tokens only: input_tokens stays unknown rather than assumed.

Wire Contract

For the exact request/response fields each adapter depends on, see contracts/voyage.md and contracts/jina.md.

See Also