Instead of fetishizing REST for its own sake, how about appreciating an HTTP API that can be used (read/written) with a browser via form elements and hrefs?
http://www.youtube.com/watch?v=Sv5woNs9WRE
Being accurate with a technical term is not a 'fetish.'
And what's the use case anyway? Are you going to perform those requests from other domains and authenticating via cookies on your own? How do you protect from CSRF doing that? What's wrong with OAuth 2.0 + JS?
It is not. It's quite complex actually. And I'm betting what most people who believe they have a clue think of "REST" is actually "RPC over pretty urls".
Actually some Google engineers do a very good job of explaining how AtomPub and GData APIs work just with short Youtube videos.