"And as for Bustle not having a public JSON API, well, here you go: curl -H "Accept: application/json" http://www.bustle.com/api/v1/sections/home.json http://ww

"And as for Bustle not having a public JSON API, well, here you go: curl -H "Accept: application/json" http://www.bustle.com/api/v1/sections/home.json http://www.bustle.com/api/v1/sections/home.json A versioned JSON API that is guaranteed not to change. Can any public site on the internet guarantee that about its HTML?" That's an interesting definition of "public JSON API" you are using. * Where is the public documentation for this endpoint? * Given an ember app, how do you arrive at that URL? (Previously you mentioned watching network requests from a browser to discover the URL endpoint, I think that's particularly unsuitable way of discovering a public JSON API) * Where's the schema definition of that JSON blob? That's as much a public JSON API as "curl http://en.wikipedia.org/wiki/Louis_Boullogne" http://en.wikipedia.org/wiki/Louis_Boullogne" is a public HTML API. And at least with the wikipedia one, there is some defined structure and implied meaning to the data coming back (i.e. standardised HTML elements). "A versioned JSON API that is guaranteed not to change." How is that guarantee enforced? What prevents a developer from changing the nature or structure of the response at that URL?