Niches · Retrieval & vector search

Return whole documents and further pages, not a pile of chunks

Two or three companies' docs show a full fit.

2companies, full fit
7companies, fit with a limit
17companies carry the tag
8share of the category's work
3first-hand accounts

What counts as done

Results are grouped by a document field so N distinct documents come back in one call, and page 2 returns the next N with no gaps or repeats. Checked with a fixture of 50 documents of 5 chunks each.

How agents ask for it: top 10 documents about X, show page 2 of the results, one result per product

Does the job 2

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
Elasticsearch C
Elasticsearch B.V.
Nested kNN stores one vector per chunk and returns parent documents ranked by their best chunk, with inner_hits for the passages; collapse also keeps one hit per field value. source
Meilisearch A
Meili SAS
A distinct attribute such as a document id returns one chunk per document, with offset and limit for the next page. source

Does the job, with a limit 7

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Chroma API + MCP D
Chroma Inc.
GroupBy on a metadata key with limit and offset exists, but only in the Cloud Search API and only with a ranking expression. source
Milvus and Zilliz Cloud API + MCP B
Zilliz Inc.
group_by_field (for example docId) returns one or group_size hits per document, but paging to the next N groups is not documented on the grouping page. source
OpenSearch BB
OpenSearch Software Foundation, a project of The Linux Foundation
Nested k-NN returns parent documents, with k counting documents and inner_hits naming the matching chunks, but paging to the next N documents was not shown. source
Qdrant API + MCP BB
Qdrant Solutions GmbH
The Grouping API groups chunk hits by a document field, but page 2 needs the docs' exclusion-filter pattern rather than an offset on groups. source
Typesense API + MCP BB
Typesense, Inc.
group_by makes per_page count groups and page walk them, but #2618 reports pages returning fewer documents than requested after mass deletions. source
Vespa BB
Vespa.ai AS
The grouping language groups hits by any field, such as a document id, with hits per group, but paging to the next N groups was not confirmed on the page read. source
Weaviate API + MCP C
Weaviate B.V.
Hybrid and vector queries take a group-by on a property with group and per-group limits, but paging to the next N groups is not shown; limit and offset apply to objects. source

Doesn't do this job 5

Listings in the category that do something else, with the reason.

ListingWhy
Cloudflare AI Search BB
Cloudflare, Inc.
No group-by or document-level collapse on search; results are chunks, and no pagination parameter appears in the search reference. source
Epsilla Vector Database E
Epsilla, Inc.
No group-by on query; record retrieval pages with skip and limit only. source
LanceDB B
LanceDB Systems, Inc.
No group-by or collapse parameter on vector or hybrid search; only limit and offset. source
Pinecone API + MCP A
Pinecone Systems Inc.
No group-by and no offset or page token on Documents API search; Drupal maintainers overshoot top_k and slice to fake both. source
Upstash Vector API + MCP B
Upstash, Inc.
No group-by on query; resumable queries and range page through raw results. source

What stops agents finishing

  • no group-by, so the agent overshoots topK and retries
  • no offset or page token on the newer search endpoints

Around it

Before: vector-search.rag-over-docs. After: search.search-with-text.

Where this comes from

Weight 8 of 100 in Retrieval & vector search: 3 of 37 accounts (Pinecone group-by and pagination from the Drupal maintainer, Typesense pagination after deletions)

The same as data: /api/v1/use-cases/vector-search.document-results.json, or the MCP tool get_use_case with id vector-search.document-results. Other jobs in this category: /api/v1/niches?category=vector-search.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.