Hi There, I think you are talking about the Asset Http API which is
mostly used for asset manipulation(crud operations) and not for search.
Searching can be done using querybuider API which is exposed @
http://localhost:4502/bin/querybuilder.json and allows parameters to be
passed on to the search engine. Please check
which will help to understand the overall big picture about AEM...
You cannot do this OOTB since rendition dimensions are not sorted as
properties. Technically could search for rendition nt:files, create a
custom QueryBuilderFiltering predicate that pulls them into memory and
determines their size and filters them in/out - but needless to say this
would be very very bad for performance -- so don't do this! Instead, I
suggest creating a WF Process (assuming 6.x) that determines and writes
rendition sizes as JCR Properties that you can then search over. There