Document Search Response (POST /v3/search)
Response from client.search.documents() and client.search.execute():
Document Result Fields
Unique identifier for the document containing the matching chunks.
Document title if available. May be null for documents without titles.
Document type (e.g., “pdf”, “text”, “webpage”, “notion_doc”). May be null if not specified.
Overall document relevance score. Combines semantic similarity, keyword matching, and metadata relevance.
- 0.9-1.0: Extremely relevant
- 0.7-0.9: Highly relevant
- 0.5-0.7: Moderately relevant
- 0.3-0.5: Somewhat relevant
- 0.0-0.3: Marginally relevant
Array of matching text chunks from the document. Each chunk represents a portion of the document that matched your query.
The actual text content of the matching chunk. May include context from surrounding chunks unless
onlyMatchingChunks=true.Chunk-specific similarity score. How well this specific chunk matches your query.
Whether this chunk passed the
chunkThreshold. true means the chunk is above the threshold, false means it’s included for context only.Document metadata as key-value pairs. Structure depends on what was stored with the document.
ISO 8601 timestamp when the document was created.
ISO 8601 timestamp when the document was last updated.
Full document content. Only included when
includeFullDocs=true. Can be very large.AI-generated document summary. Only included when
includeSummary=true. Provides a concise overview of the document.Memory Search Response
Response fromclient.search.memories():
When searchMode="memories" (default), all results are memory entries:
searchMode="hybrid", results can contain both memory entries and document chunks. Memory results have a memory key, chunk results have a chunk key:
Distinguishing Memory vs Chunk Results:In hybrid mode, check which key exists on the result object:
- Memory results: Have a
memorykey (nochunkkey) - Chunk results: Have a
chunkkey (nomemorykey)
Memory Result Fields
Unique identifier for the memory entry or chunk ID. In hybrid mode, can be either a memory ID (e.g.,
mem_xyz789) or a chunk ID (e.g., chunk_abc123).Complete memory content. Only present for memory results (when
searchMode="memories" or when a memory result is returned in hybrid mode). This field is not present for chunk results.Chunk content from a document. Only present for chunk results when
searchMode="hybrid". This field is not present for memory results. Contains the actual text content from the document chunk.Similarity score between your query and this memory. Higher scores indicate better matches.
- 0.9-1.0: Extremely similar
- 0.8-0.9: Very similar
- 0.7-0.8: Similar
- 0.6-0.7: Somewhat similar
- 0.5-0.6: Marginally similar
Memory metadata as key-value pairs. Structure depends on what was stored with the memory.
ISO 8601 timestamp when the memory was last updated.
Version number of this memory entry. Used for tracking memory evolution and relationships. For chunk results, this is typically
1.Root memory ID for memory entries. Only present for memory results. Always
null for chunk results.Contextual memory relationships. Only included when
include.relatedMemories=true.Array of parent memories that this memory extends or derives from.
Array of child memories that extend or derive from this memory.
Context Memory Structure
Content of the related memory.
Relationship type:
"updates", "extends", or "derives".- updates: This memory updates/replaces the related memory
- extends: This memory builds upon the related memory
- derives: This memory is derived from the related memory
Relative version distance:
- Negative values for parents (-1 = direct parent, -2 = grandparent)
- Positive values for children (+1 = direct child, +2 = grandchild)
When the related memory was last updated.
Metadata of the related memory.
Associated documents. Only included when
include.documents=true.Document identifier.
Document title.
Document type.
Document metadata.
Document creation timestamp.
Document update timestamp.