List or search memories
Without q: lists memories (optionally namespace-filtered). With q: semantic search via Kairos recall (top 20), results carry a score. Class A — all three lanes.
NAMESPACE SCOPING: ns is checked against the credential's scoped_namespaces after the credential is authenticated and authorized, so an out-of-scope ns is a 403 (never a 401). A credential restricted to exactly ONE namespace and omitting ns has that namespace injected; one restricted to two or more must name one.
FILTERING IS SERVER-SIDE AND CHEAPER. tag, source, since and until are applied by the engine BEFORE it hydrates any memory text, so a filtered page transfers (and meters) only the rows that matched. Filtering the returned array instead bills you for the whole namespace on every call — prefer these parameters in every case.
PAGINATION: feed nextCursor back as cursor. Filters apply BEFORE pagination, so a cursor is only meaningful when replayed with the SAME filters; change a filter and start again with no cursor. nextCursor is absent on the last page.
The filter and cursor parameters apply to the LIST path only. Combining any of them with q is a 422, not a silently ignored filter — search ranks by relevance and cannot filter on them. Drop q to filter, or drop the filters to search.
Requires the memories:read scope. Accepts all three lanes: a session JWT (bounded by the caller's role on this workspace) or an il_* machine credential whose own scope set, workspace set and validity window cover it — both ceilings apply and neither can raise the other, so a credential carrying memories:read is still refused where the role does not permit it.
A credential with no scope record resolves to LEGACY_DEFAULT, which INCLUDES memories:read — every key minted before scoping keeps working here.
Request
- Base URL: https://api.infolang.ai
- URL: https://api.infolang.ai/v2/workspaces/{id}/memories
- Auth: one of:
- HTTP bearer
- HTTP bearer
- HTTP bearer
Path parameters
Query parameters
Opaque token from the previous page's nextCursor.
Keep memories whose tag set contains this exact value.
Exact match against the memory's source.
Inclusive lower bound on timestamp, epoch MILLIseconds.
Inclusive upper bound on timestamp, epoch MILLIseconds.
Response
Memories
Changes
No recorded changes to this operation across all 1 revision of this API.