Parameters
The customer identifier to fetch context for. Required on B2B; auto-resolved on B2C — see B2C vs B2B.
Optional conversation identifier. When provided, results are biased toward memories relevant to the active conversation. When supplied, it must be a valid UUID registered via
record_message.One or more search queries to find relevant customer memories. If omitted, returns the most recent and highest-confidence customer-scoped memories.
Maximum number of memory items to return. Defaults to
10. Maximum 50.Filter results to specific memory types. If omitted, all types are included.
| Value | Description |
|---|---|
fact | Factual information about the customer organization |
preference | Customer organizational preferences |
episode | Significant events within the customer organization |
emotion | Sentiment and emotional context within the organization |
temporal_event | Time-bound events (project deadlines, fiscal year, etc.) |
Retrieval mode that controls the speed-quality tradeoff — the retrieval axis (
For real per-mode latency on your instance, see Dashboard → Usage.
fast vs accurate) of Retrieval Modes.| Value | Description |
|---|---|
fast | Vector search only. Lower latency. Default. |
accurate | Full vector + graph + re-ranking. Higher quality, higher latency. |
Returns
AContextResponse with the following fields:
Array of fact memories relevant to the query.
Array of preference memories.
Array of episode memories.
Array of emotion memories.
Response metadata including
total_results, query_time_ms, tokens_used, scope, and mode.Example
Response
Raises
InvalidInputError— whenmodeis not"fast"or"accurate".SDKNotInitializedError— when called beforeawait sdk.initialize().AuthenticationError— when the API key is invalid or revoked.ContextNotFoundError— whencustomer_iddoes not exist for this instance.
See also
sdk.user.context.fetch— user-scoped contextsdk.client.context.fetch— organizational (client) contextsdk.context.fetch— unified scope-chain fetch