Comments on a Hacker News story, flattened, with depth and parent id.

The comments on a Hacker News story, flattened, each with depth and parent id. SAME UPSTREAM DOCUMENT as hackernews/story -- hn.algolia.com/api/v1/items/{id} already carries the comment tree in children, and the story route discards it on purpose. There is no new upstream call here; there is exposure of what already arrived. Measured on item 8863: 32 children, 104 points. An empty list is an answer (a story with no comments is charged, the question was answered); an id that does not exist is a real 404 and costs no credit. THE ANCHOR HERE IS id, NOT title: /items/{id} answers 200 for a story and for a comment alike, and this route requires only id -- measured, a comment id is accepted with 200 and comes back with the replies to THAT comment and title null. Whoever needs to tell a story from a comment has to read title in the response, because this route does not do it for them. The sibling route hackernews/story DOES refuse a comment, because it requires title.