No, lol. I like the way asp.net urls are supposed to work. That is, simple routes in plain english. It never works out that way though. I think the end goal should be to make it as easy on the user as possible. So to me that means doing any heavy lifting possible so the user doesn't have to.

Just think about paging. As soon as I see paging I know I have to create a whole JavaScript state machine to keep track of the index and etc. I think that's hostile to the user. Give me everything even if it's just an array of ID's so that I dont have to make that state machine.

Another example I gave was having multiple urls for the same image. I really do not think that's practical. If you need something like a high definition download put that in its own section of the API. For 99.9% of use cases the normal image will do.

Just K.I.S.S. Before you write anything stop and think if you can say it in a more plain way.