Retriever Templates
21 pre-configured retriever templates for common search patterns like semantic, faceted, and RAG
Why do anything?
Building retrievers from scratch is time-consuming. Templates provide proven starting points.
Why now?
Common search patterns are well-understood. Encoding best practices in templates saves time.
Why this feature?
21 retriever templates covering semantic search, faceted search, RAG preparation, anomaly detection, and more.
How It Works
Retriever templates provide pre-configured stage pipelines for common search patterns.
1
Template Selection
Choose from 21 available templates
2
Parameter Binding
Bind template variables to your context
3
Stage Generation
Generate retriever stages from template
4
Deployment
Deploy configured retriever to namespace
Why This Approach
Templates encode best practices. Variable binding enables customization without rebuilding.
Where This Is Used
Integration
retriever = client.retrievers.from_template(template_id="semantic_search", params={...})Recent updates
Full changelog- Jul 5, 2026Starter retriever templates fixed, plus Explain Plan polishEvery retriever starter template now creates a working retriever. Two templates carried outdated stage configurations that made their retrievers uncreatable, and template configs are now validated against the live stage registry in CI so they stay correct. Explain Plan output now lists stages in execution order with the first stage on top, and it is opt-in per run so default executions stay fast. Retriever evaluations also no longer fail intermittently, and a false feature index warning is gone.
- Jul 3, 2026Filter operators now work as written (no more silent equality)Retriever and object-list filters now honor every operator on string and date fields. Previously ne, gt/gte/lt/lte, and contains/starts-with/ends-with on a string value were silently collapsed to exact-match equality (and ne was even inverted), so a filter like created_at >= <date> could return zero over hundreds of matching records. Now each operator keeps its meaning, *_at fields coerce ISO-8601 dates and match either stored format, and text operators use literal substring semantics. Existing filters just start returning the right rows; no change needed on your side.
- Jul 1, 2026Explain Plan for retriever executionsEvery retriever run can now show an Explain Plan — a database-style visual tree of the stages that ran (recall, filters, rerank, fusion) alongside the raw output — so you can see exactly why a query returned what it did and where the time went. Toggle it on from any execution.
- Jun 24, 2026Per-stage latency budgets for retrieversRetriever stages now honor a hard per-stage timeout ceiling, so a slow LLM stage (summarize, query-expand) degrades gracefully instead of hanging the whole request. Timed-out searches return a clear degraded status rather than a silent empty result.