Boolean Recall
Deterministic full-text search – exact term matching, no embeddings.
When to use it
/recall/boolean_recall runs a BM25-style full-text search. It’s the right tool when:
- Exact terms matter – product codes, error codes, legal terms, regulatory IDs
- Auditability matters – compliance searches need provable matches, not “semantically similar”
- Speed matters – no embedding inference, no graph traversal, no reranking
full_recall when the query is a literal lookup, not a semantic question.
Endpoint
- Auth: Bearer token
- Idempotency: Read-only
- Async: No
Example
Request parameters
Operators
Response
Same shape asPOST /recall/full_recall.
relevancy_score reflects BM25 scoring rather than semantic similarity.
Boolean vs full recall
Behavior notes
phrase operator is order-sensitive. “30 days refund” will not match “refund within 30 days.” Use and if you want all terms regardless of order.Related endpoints
- For semantic search: Full recall – embeddings + graph
Errors
Common codes:400 INVALID_PARAMETERS, 404 TENANT_NOT_FOUND, 422 VALIDATION_ERROR, 429 RATE_LIMITED. See Error Responses for the full list.
Read more: Essentials → RecallAuthorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Unique identifier for the tenant/organization
"tenant_1234"
Search terms to find in your content
"John Smith Jake"
Optional sub-tenant identifier used to organize data within a tenant. If omitted, the default sub-tenant created during tenant setup will be used.
"sub_tenant_4567"
How to combine search terms: 'or' (any term matches), 'and' (all terms must match), 'phrase' (exact phrase must appear)
or, and, phrase "and"
Maximum number of results to return
1
What to search: 'sources' for documents or 'memories' for user memories
sources, memories Response
Successful Response
Result of a hybrid search retrieval operation.
Deduplicated source documents corresponding to the returned chunks
Graph context containing query-based paths and chunk-based relation paths.
Map of chunk_uuid to VectorStoreChunk for extra context from forcefully related sources. Use chunk.extra_context_ids to look up chunks: extra_context[id] for id in chunk.extra_context_ids.