From 10888a94bca35ba5f5bc32f719fb9bcfe5bb08d2 Mon Sep 17 00:00:00 2001
From: sohamd22 <85427822+sohamd22@users.noreply.github.com>
Date: Tue, 6 Oct 2026 16:48:37 +0000
Subject: [PATCH] docs(api): note related memory ids in v5 search (#1767)

Docs for supermemoryai/mono#3418: related memories in search carry `id`.
---
 apps/docs/snippets/api-v5-search.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/apps/docs/snippets/api-v5-search.mdx b/apps/docs/snippets/api-v5-search.mdx
index 4cf919f9..98132b28 100644
--- a/apps/docs/snippets/api-v5-search.mdx
+++ b/apps/docs/snippets/api-v5-search.mdx
@@ -53,7 +53,7 @@ Legacy `include.chunks` has no v5 equivalent. Choose `chunks` or `hybrid` instea
 `include` is an object of booleans in the body, e.g. `"include": {"documents": true, "related": true}`. Each flag defaults to `false`.
 
 - `include.documents` adds the most relevant source document to each result.
-- `include.related` adds parent, child, and sibling memories.
+- `include.related` adds parent, child, and sibling memories. Related memories come only from the same namespace and must match the request's `filter`, so they never surface content the search itself would exclude.
 - `include.forgotten` lets forgotten and expired memories appear in results, including as primary results.
 - `rerank` accepts `none`, `order`, or `aggregate`; `rewriteQuery` controls retrieval-oriented query rewriting.
 
@@ -64,7 +64,7 @@ Legacy `include.chunks` has no v5 equivalent. Choose `chunks` or `hybrid` instea
 | Result array | `results` |
 | Timing | `searchTime` |
 | Source expansion | `result.included.document`, with timestamps under its `system` |
-| Related context | `result.included.related.{parents,children,siblings}` |
+| Related context | `result.included.related.{parents,children,siblings}`, each with its memory `id` |
 | Lifecycle fields | `result.system` |
 | Version and inference flags | `result.isLatest`, `result.isInference` |