Hacker News 帖子评论 API
通过 id 列出 Hacker News 帖子下的评论：内容、作者和时间戳，以干净的 JSON 返回。
US$1.50/千次请求，按请求付费，无需订阅。
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"}
价格与服务商
Hacker News 帖子评论 API 价格：一个 API，2 个可互换的服务商
最便宜的服务商优先响应。如果它失败，下一个会在同一次调用中接手。
试一试
一个请求获取 Hacker News 帖子评论
这个示例展示了 11 个字段中的 10 个。查看全部字段
{
"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"
}
]
}
}完整的参数与响应参考：这个接口的每个字段、类型和示例。
参考
一个请求，一种响应结构。
你发送的每个字段和收到的每个字段，都附有真实示例。
最近验证于 2026-11-14 · 可用率和延迟按 30d 统计
请求体
JSON，POST 到这个接口。
- idstring
45389217
Hacker News 帖子 id，例如 "47340079"。
响应
JSON，每个字段一个示例值。
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.
常见问题
关于 Hacker News 帖子评论 API
AnyAPI 的 Hacker News 帖子评论 API 只需一次 POST 请求 /v1/run/hackernews.story_comments，就以统一格式的 JSON 返回 Hacker News 数据。通过 id 列出 Hacker News 帖子下的评论：内容、作者和时间戳，以干净的 JSON 返回。AnyAPI 会在 2 个数据源之间路由每个请求，某个数据源失败时自动切换。费用：每千次请求 US$1.50 起，以美元计价，无需订阅，也没有每月最低消费。过去 30 天，通过 AnyAPI 发起的 Hacker News 帖子评论 API 调用中有 100.0% 成功，响应时间中位数为 0.6 秒，共测量 261 次调用。