@abadesi Thanks for hunting. The usual way would be to add query parameters for sorting, filtering, and pagination to every GET action in all your controllers. Then handle the code for that in every action, resulting in lots of duplicate code that's frankly tedious to write & maintain in a project with many controllers. Sometimes you even end up writing a micro-DSL (ie. comma separated sort/filter values) for every project. Instead, you can let Sieve take care of all that in a semi-standardized way and write less code (check out Sieve's source).