Designing REST endpoint for starting all modules

I’ve started work on implementing moduleaction resource, and I’m stuck on:

MainResourceController treats module and action as search parameters and tries to run search. Implementing Searchable to execute actions seems to be ugly hack. I thought about introducing new interface, e.g. Executable, but I don’t know how we could cleanly differ in controller, whether request parameters are execution or search parameters.

What do you think? @raff, @burke, @dkayiwa, @wyclif