TokenPath vs Voyage AI

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	TokenPath RAG	Voyage AI RAG
Tagline	Token-level citation and attribution API for AI-generated answers	State-of-the-art embedding models and rerankers purpose-built for retrieval and RAG.
Category	RAG	RAG
Pricing	Freemium· 10M tokens free to start (no card), then $1 per 1M tokens pay-as-you-go	Freemium· Free tier: 200M free text tokens per account for current models (50M for older specialized). Text embeddings $0.00002–$0.00018 per 1K tokens depending on model tier. Rerankers $0.00002–$0.00005 per 1K tokens after 200M free. Multimodal $0.12 per 1M text tokens + $0.60 per 1B pixels. Batch API 33% discount. File storage $0.05/GB/month.
Model	model-agnostic (works with any LLM output; uses in-house attribution model)	in-house (voyage-3.5, voyage-4 series, voyage-code-3, voyage-finance-2, voyage-law-2, voyage-multimodal-3.5, voyage-context-3, rerank-2.5)
Editorial score	—	—
Use cases	RAG chatbot citationcontract and policy Q&Acustomer support groundinginternal knowledge base searchcompliance and audit trails for AI answersfaithfulness evaluation in eval pipelinesclinical and legal document assistantsresearch assistant sourcing	Production RAG chatbot over proprietary docsTwo-stage retrieval with embed + rerankCode search across a monorepoLegal contract semantic searchFinancial filings and research retrievalMultimodal image-and-text searchLong-context document embedding (32K tokens)Context-aware chunk embedding for dense passagesBatch embedding of large historical corporaMongoDB Atlas Vector Search backends
Pros	Model-agnostic — works with any LLM output, not tied to a single provider or fine-tune Runs post-generation, so no need to re-prompt or restructure existing RAG pipelines Token-level granularity with confidence scores rather than coarse chunk-level citations Fast enough for interactive use (sub-two-second on 20k-token documents) Published benchmark number (0.815 F1) gives a concrete accuracy baseline to reason about Cheap, transparent pricing ($1/M tokens) with a generous 10M-token free tier and no card required Solves a real, common RAG failure mode — hallucinated or drifting citations	Consistently near the top of MTEB and BEIR retrieval leaderboards — measurable recall gains over OpenAI text-embedding-3-large in most public evaluations. Short output dimensions (as low as 256 or 512) cut vector storage and ANN latency 3x–8x versus 1536/3072-dim competitors. Domain-tuned models (code, finance, legal) meaningfully outperform general embeddings on in-domain corpora. voyage-context-3 embeds chunks with awareness of surrounding document context, reducing the classic 'lost context' problem in fixed-window chunking. Rerank-2.5 with instruction-following gives a clean two-stage retrieval pipeline without training a custom cross-encoder. Generous 200M-token free tier per account makes prototyping and small production workloads essentially free. Batch API offers a 33% discount for large offline embedding jobs. MongoDB acquisition (2025) means tight, ongoing integration with Atlas Vector Search.
Cons	Narrow scope — only citation/attribution, not retrieval, generation, or a full RAG framework Adds an extra API round-trip and token cost on top of the underlying LLM call Public documentation is thin on SDKs, language coverage, and enterprise features like SSO/VPC deployment 0.815 F1 still means a non-trivial share of attributions are wrong, so it does not remove the need for human review in high-stakes domains Effectiveness depends on how well the source document was actually surfaced in-context — garbage retrieval in, garbage attribution out Young product with limited independent benchmarks or case studies from third-party users	API-only closed models — no self-hosting option, so latency-sensitive or air-gapped deployments are ruled out. Not an end-to-end RAG stack — you still need a vector database, LLM, and orchestration layer, which increases integration surface. Post-MongoDB acquisition, product roadmap and standalone longevity depend on MongoDB's priorities. Domain models cover finance, legal, and code but nothing else — medical, scientific, or multilingual-heavy corpora fall back to general models. Documentation is competent but sparser than OpenAI's or Cohere's — fewer end-to-end recipes for advanced patterns like hybrid search or query expansion. Pricing per token is competitive but not the cheapest — self-hosted open models (e.g. BGE, E5) are free at inference if you have GPUs.
Website	tokenpath.ai	www.voyageai.com

Pick TokenPath if

✅ Model-agnostic — works with any LLM output, not tied to a single provider or fine-tune
✅ Runs post-generation, so no need to re-prompt or restructure existing RAG pipelines
✅ Token-level granularity with confidence scores rather than coarse chunk-level citations
✅ Fast enough for interactive use (sub-two-second on 20k-token documents)

Pick Voyage AI if

✅ Consistently near the top of MTEB and BEIR retrieval leaderboards — measurable recall gains over OpenAI text-embedding-3-large in most public evaluations.
✅ Short output dimensions (as low as 256 or 512) cut vector storage and ANN latency 3x–8x versus 1536/3072-dim competitors.
✅ Domain-tuned models (code, finance, legal) meaningfully outperform general embeddings on in-domain corpora.
✅ voyage-context-3 embeds chunks with awareness of surrounding document context, reducing the classic 'lost context' problem in fixed-window chunking.

Compare a different pair →