List memories with cursor-based pagination.
Cursor-based pagination is more efficient for large datasets and handles data changes better than offset-based pagination.
Args: user_id: Optional user ID to filter memories cursor: Cursor from previous response for next page (None for first page) limit: Number of items per page (default: 50, max: 100) sort_by: Field to sort by (default: ‘updated_at’) sort_order: Sort order - ‘asc’ or ‘desc’ (default: ‘desc’)
Returns: MemoryListResponse with memories and next_cursor
Examples: First page: GET /memories?user_id=user_123&limit=50
Next page (using cursor from previous response): GET /memories?user_id=user_123&cursor=mem_xyz123&limit=50
Sort by updated_at descending (most recent first): GET /memories?user_id=user_123&sort_by=updated_at&sort_order=desc
Sort by memory_id ascending: GET /memories?user_id=user_123&sort_by=memory_id&sort_order=asc
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
The workspace ID
User ID to filter memories
Cursor for pagination (use next_cursor from previous response)
Number of memories to return per page
1 <= x <= 100Field to sort memories by (e.g., 'memory_id', 'updated_at')
Sort order (asc or desc)
asc, desc Successful Response
Schema for listing memories with cursor-based pagination.