Search infrastructure
Search is evolving, and every agent needs different search. Developers need choice. SearchRouter puts every provider behind one API, with automatic fallback and unified billing.
Routes across
exatavilyparallelvalyuseltzserperbravelinkupperplexityfirecrawlscrapflyapifyopenaicoherevoyagejinazeroentropyfireworksmixedbread
Drop-in
The request shape never changes. Point your existing search and embeddings code at one base URL, set a model slug like exa/neural or cohere/rerank-v3.5, and let the router pick the endpoint. Add a provider block to route by price, latency, or quality.
Fan outmode: fanout
exatavilybravequeried concurrently
Fused ranking
1Comparing vector databases for RAG
tavilyexabrave
2Hybrid search: BM25 + embeddings
exabrave
3Benchmarking retrieval recall
tavily
Mix & match
You are not locked to a single provider per query. Fan out across several engines in one request, then dedupe and fuse the rankings so results multiple engines agree on rise to the top. Every result shows which engines returned it.
Why a router
No single engine is best at every query. SearchRouter is the control plane for the many-model search era.
The surface
Create a key and run your first query against any provider. Demo mode works with zero upstream credentials.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。