I'd been hesitant but put it in the original content api after reading @bruntonspall's piece about the guardian's approach - http://www.theguardian.com/info/developer-blog/2012/jul/16/http-status-codes-jsonp - but it does seem the important thing is a predictable way to test for errors other than by reading the status code, rather than that having to be an explicit status.