Semantic search over memories
POST/api/v1/llm/search-memories
Searches memories by meaning within the authenticated user's tenant scope. Results and relationships depend on the configured provider. An empty result can represent a handled provider failure and does not prove that no memories exist. Search does not provide pagination or a complete inventory.
Use an authorized backend key with X-On-Behalf-Of and users:impersonate scope, or a publishable key with a user JWT. A configured user JWT can also authenticate directly. An effective user and tenant are required; raw identity headers do not grant authority. See the memory cookbook.
Request
Responses
- 200
- 400
- 401
- 403
- 500
- 502
- 503
- default
Search results returned
Invalid decoded request, including omitted topK or values outside their bounds, or missing tenant context.
Missing or invalid authentication, or no effective user.
Insufficient impersonation scope or required tenant membership.
Unexpected server failure.
Authentication upstream returned an unreadable or invalid response.
Authentication service unavailable.
Other failures may be forwarded from upstream. Error bodies vary by origin; this slice does not assert a single error envelope.
Document ID: DOC-MA-conversations-api-searchMemories. Section identities and revisions.
| Section | Stable reference |
|---|---|
| Overview | DOC-MA-conversations-api-searchMemories#overview |
| Request | DOC-MA-conversations-api-searchMemories#request |
| Responses | DOC-MA-conversations-api-searchMemories#responses |