Skip to main content
POST
Full-text search

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
Use this instead of 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 as POST /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.
  • 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 → Recall

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
tenant_id
string
required

Unique identifier for the tenant/organization

Example:

"tenant_1234"

query
string
required

Search terms to find in your content

Example:

"John Smith Jake"

sub_tenant_id
string | null

Optional sub-tenant identifier used to organize data within a tenant. If omitted, the default sub-tenant created during tenant setup will be used.

Example:

"sub_tenant_4567"

operator
enum<string>
default:or

How to combine search terms: 'or' (any term matches), 'and' (all terms must match), 'phrase' (exact phrase must appear)

Available options:
or,
and,
phrase
Example:

"and"

max_results
integer
default:10

Maximum number of results to return

Example:

1

search_mode
enum<string>
default:sources

What to search: 'sources' for documents or 'memories' for user memories

Available options:
sources,
memories

Response

Successful Response

Result of a hybrid search retrieval operation.

chunks
VectorStoreChunk · object[]
Example:
sources
SourceInfo · object[]

Deduplicated source documents corresponding to the returned chunks

graph_context
GraphContext · object

Graph context containing query-based paths and chunk-based relation paths.

additional_context
Additional Context · object

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.