Yes, I am aware of my own answer pointing out the new json endpoint in the doc. Thanks.

I don't understand why the stackexchange API would use this custom non-standard response format instead of a standard JSON object that most REST api libraries understand. Also inconsistent with most of the rest of the API which uses JSON.

sorry, what isn't clear about the question? is there skepticism about whether the API actually sends back the content-type and response as stated?