Hacker News Commenti della storia API
Elenca i commenti a una storia di Hacker News tramite id - testo, autore e timestamp come JSON pulito.
1,50 USD/1k richieste, paghi a richiesta, nessun abbonamento.
gwern_reader Sep 27, 2025 | next [-]
The interesting bit here is not Rust itself, it is that they went from a 40 minute cold build to under 3 minutes by caching at the crate graph level instead of the file level. That is a build system design decision, not a language one.
reply
{"id": "45389802","parentId": "45389217","author": "gwern_reader","text": "The interesting bit here is not Rust itself, it is that they went from a 40 minute cold build to under 3 minutes by caching at the crate graph level instead of the file level. That is a build system design decision, not a language one.","createdUtc": 1758981900,"postId": "45389217","permalink": "https://news.ycombinator.com/item?id=45389802"}
Prezzi e provider
Prezzi dell'API Hacker News Commenti della storia: una sola API, 2 provider intercambiabili
Serve per primo il provider più economico. Se fallisce, subentra il successivo nella stessa chiamata.
Provalo
Ottieni Hacker News Commenti della storia in una sola richiesta
Questo esempio mostra 10 campi su 11. Vedi tutti i campi
{
"found": true,
"data": {
"comments": [
{
"id": "45389802",
"parentId": "45389217",
"author": "gwern_reader",
"text": "The interesting bit here is not Rust itself, it is that they went from a 40 minute cold build to under 3 minutes by caching at the crate graph level instead of the file level. That is a build system design decision, not a language one.",
"createdUtc": 1758981900,
"postId": "45389217",
"permalink": "https://news.ycombinator.com/item?id=45389802"
},
{
"id": "45389944",
"parentId": "45389802",
"author": "tuple_of_one",
"text": "Bazel does crate level caching too if you use rules_rust, curious why they rolled their own instead.",
"createdUtc": 1758983160,
"postId": "45389217",
"permalink": "https://news.ycombinator.com/item?id=45389944"
},
{
"id": "45390110",
"parentId": "45389217",
"author": "kvasir_dev",
"text": "Author here. We looked at Bazel first, the migration cost for our existing Go and TypeScript services was the blocker, not the caching model.",
"createdUtc": 1758984720,
"postId": "45389217",
"permalink": "https://news.ycombinator.com/item?id=45390110"
}
]
}
}Riferimento completo di parametri e risposta - ogni campo, tipo ed esempio per questo endpoint.
Riferimento
Una richiesta, una sola forma di risposta.
Ogni campo che invii e ogni campo che ricevi, ciascuno con un esempio reale.
Ultima verifica 2026-11-21 · disponibilità e latenza misurate su 30d
Corpo della richiesta
JSON, inviato a questo endpoint.
- idstring
45389217
Id della storia di Hacker News, es. "47340079".
Risposta
JSON, un valore di esempio per campo.
Comments on the story. Populated whenever the provider has data for the entity.
- authorstring
gwern_reader
Commenting user's username. Populated whenever the provider has data for the entity.
- createdUtcnumber
1758981900
UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds. Populated whenever the provider has data for the entity.
- idstring
45389802
Hacker News comment id. Populated whenever the provider has data for the entity.
- parentIdstring
45389217
Id of the parent item (story or comment) this reply belongs to.
- permalinkstring
https://news.ycombinator.com/item?id=45389802
Permalink to the item on news.ycombinator.com.
- postIdstring
45389217
Hacker News item ID of the story the comment belongs to.
- textstring
The interesting bit here is not Rust itself, it is that they went from a 40 minute cold build to under 3 minutes by caching at the crate graph level instead of the file level. That is a build system design decision, not a language one.
Comment body text.
- foundboolean
true
True when the story id resolved and comments were returned.
- reason"not_found"
Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost.
FAQ
Sull'API Hacker News Commenti della storia
L'API Hacker News Commenti della storia di AnyAPI restituisce dati Hacker News come JSON normalizzato da una sola chiamata POST a /v1/run/hackernews.story_comments. Elenca i commenti a una storia di Hacker News tramite id - testo, autore e timestamp come JSON pulito. AnyAPI instrada ogni richiesta su 2 fonti e passa automaticamente a un'altra quando una fallisce. Costa da 1,50 USD ogni 1.000 richieste, in dollari statunitensi, senza abbonamento e senza minimo mensile. Negli ultimi 30 giorni, il 100,0% delle chiamate Hacker News Commenti della storia tramite AnyAPI è riuscito, con un tempo di risposta mediano di 0,6 secondi su 310 chiamate misurate.