1.  [](/)
2.  [Diagrams](/diagrams)
3.  Anatomy of a Retriever Pipeline

[Back to Diagrams](/diagrams)Diagram Series

# Anatomy of a Retriever Pipeline

Anatomy of a Retriever Pipeline

![Anatomy of a retriever pipeline: a query flows through staged operations (filtering, first-stage dense or hybrid search, then reranking) with each stage narrowing and reordering candidates before results are returned.](/diagrams/retriever-pipeline.webp)Full screen

Anatomy of a Retriever Pipeline

What is a retriever pipeline?

Most search APIs give you one thing: vector similarity. You pass a query, get back the top-K nearest embeddings. Done.

But real retrieval is never one step. After the similarity call you still need to filter by metadata, rerank with a cross-encoder for precision, deduplicate near-identical results, enrich with context, and reduce to the right shape. That logic lives in your application code: fragile, hard to measure, impossible to iterate without redeploying.

A retriever pipeline makes each step explicit and composable.

You define stages in JSON. Each stage processes the output of the previous one:

1\. Search: vector similarity across dense, sparse, or multi-vector embeddings

2\. Filter: metadata predicates, LLM-based semantic filtering, deduplication

3\. Rank: cross-encoder reranking, MMR for diversity, score normalization

4\. Enrich: LLM-generated fields, taxonomy classification, RAG preparation

5\. Reduce: aggregate, group, cluster, limit, summarize

The pipeline is stored, versioned, and callable as a single endpoint. Swap stages without touching application code. Benchmark with NDCG, MRR, and Recall. Track interaction signals to learn optimal weights over time.

31 stages. Under 100ms. Callable by LLM agents via MCP.

mixpeek.com/retrievers

Run this on your own data

Mixpeek turns video, images, audio, and documents in your object storage into searchable, timestamped results through one API.

[Search your own data](https://studio.mixpeek.com/namespaces/create?mode=managed&utm_source=homepage&utm_medium=diagram_detail&utm_campaign=mvs_onramp)

## Related diagrams

[

![The multimodal warehouse in one flow: extract signals from media (faces, scenes, speech, on-screen text, embeddings) so pixels become rows at ingest, index that meaning next to the bytes so it is queryable forever after one read, and retrieve by meaning with hybrid search and reranking, served to humans and agents the same way. Extract, index, retrieve; everything else is implementation detail.](/diagrams/foundations/multimodal-warehouse.webp)

Extract, index, retrieve: the whole loop



](/diagrams/multimodal-warehouse)