logo
JP

Hacker News Keyword Search

Find public Hacker News stories by keyword and publication period, ordered by relevance, date or points.

開発者
料金
$0.0005 / 件
最終更新
2026-11-11

概要

Collect public technology stories in a table that connects each topic to the stories discussing it. Titles, publication dates, article links and discussion activity help distinguish a widely discussed announcement from a result that merely mentions the same words.

The results bring topic discovery and community response together. They give researchers a starting set of reading material and give product teams context about which stories attracted attention, without requiring them to copy story details and engagement figures individually.

Data notes

Results come from a searchable index of public Hacker News submissions. Relevance ordering prioritizes search matches; chronological ordering compares publication times; hottest ordering compares points and then comment counts within a relevance-selected set of matching stories. Each row belongs to a keyword and a story. The same story can appear for different keywords, which preserves the relationship between a topic and its matches. Match ID stays stable for the same trimmed keyword and story; Story ID identifies the underlying story across topics.

Points and Comments reflect the values returned when collected and can change between runs. They describe accumulated discussion activity, rather than readership, product adoption or sentiment. Hottest results are not a complete popularity ranking of every matching submission and do not represent a time-decayed trending score. Published at refers to the submission's publication time in UTC, rather than the time an article was originally written. Calendar-date boundaries include the entire selected UTC days, while rolling periods are measured backward from the same run-start instant for every keyword. A missing count is represented by zero, and missing text by an empty value.

Article URL may be empty for a submission that consists of a question or discussion. Discussion URL still identifies its conversation. Story text contains the submission body when available, with formatting removed; it does not contain the linked article or individual comments. Search results are a selected view of matching submissions and do not establish that every relevant historical story has been included.

What the results look like

Each record represents one story matching one keyword; these sample activity figures can change over time.

KeywordStory IDTitlePointsCommentsPublished at
python45751400Uv is the best thing to happen to the Python ecosystem in a decade221413242025-10-29T18:57:29Z
python20915746Sunsetting Python 216167042019-09-09T06:43:24Z

Other columns include Article URL, Discussion URL, Author, Match ID and Story text.

Use cases

  • Prioritize reading: compare Title, Points and Comments to choose stories for closer review, then use Discussion URL to inspect the conversation.
  • Compare topics: group results by Keyword and compare the distribution of Points and Comments to understand the activity around the returned stories, while accounting for overlaps using Story ID.
  • Trace a topic over time: use Published at and Title to compare early discussions with later announcements; combine Story ID and Match ID to update repeated collections without duplicating the same topic-story pair.

適用範囲と境界

Public stories only, up to 20 keywords and 1,000 returned stories per keyword; hottest ranks at most 1,000 relevance-selected candidates, and search availability may return fewer matches.

  • 適している用途
  • Find stories about technologies, products or companies discussed by developers.
  • Collect comparable topic results with publication dates and discussion activity.
  • Compare recent coverage with earlier stories or examine topic activity within a publication period.
  • 適さない用途
  • You need comment bodies, complete linked articles, or exhaustive historical coverage.
  • You need current front-page rank, a time-decayed trending score, or guaranteed highest scores across every matching story.

失敗時の処理

開発者が宣言した失敗時と再試行の動作です。連携時にはシステムプロンプトに含めることをおすすめします。

  1. 1For an empty result, try a broader or differently worded keyword; an empty result is valid.
  2. 2If search is temporarily unavailable or rate limited, retry later; earlier returned rows may remain after a failure.
  3. 3If the run times out, reduce the number of keywords or the per-keyword limit and retry.
  4. 4Repeated identical keywords are trimmed and processed once; use a list containing one string for a single search.
  5. 5Use valid YYYY-MM-DD dates with the start on or before the end; periods with no overlap return no stories.
  6. 6If oldest-first search is too broad, use a narrower publication period or more specific keywords.

入力

この App の呼び出しに必要なパラメータで、manifest.json の input.schema から生成されています。

  • Keywordskeywords必須array<string>
    Search each string independently. Supply 1 to 20 non-empty strings; repeated identical keywords are processed once.
    件数最大 20 件例["python"]
  • Limit per keywordlimit_per_keyword任意integer
    Maximum stories returned for each keyword, from 1 to 1,000; defaults to 100. Searches with fewer available matches return fewer stories.
    範囲1–1000デフォルト100
  • Sort ordersort_by任意string(enum)
    Choose how stories are ordered; defaults to relevance. Hottest sorts up to 1,000 relevance-selected matches by points, then comments, and does not guarantee the highest score across all matches.
    選択可能な値Most relevantrelevanceNewest firstnewestOldest firstoldestHottest (points, then comments)hottestデフォルトrelevance
  • Time rangetime_range任意string(enum)
    Restrict publication time to a rolling period ending at run start; defaults to all time. If custom dates are also supplied, only the overlapping period is searched.
    選択可能な値All timeallPast 24 hourslast_24hPast 7 dayslast_7dPast 30 dayslast_30dPast 365 dayslast_yearデフォルトall
  • Custom date rangedate_range任意object
    Optionally restrict publication time by UTC calendar dates, including both boundary days. Missing dates leave that side open; combined with Time range, only the overlap is searched.

出力

1 件のレコードのフィールド構造で、manifest.json の output.schema から生成されています。

  • Match IDidstring
    Stable identifier for the exact trimmed keyword and story pair.
    例759cbfc402d5206e48b00a01788e8f5af14e87a83916eb4f340586d316485a0e
  • Keywordkeywordstring
    The trimmed search string that matched this story.
    例python
  • Story IDstory_idstring
    Hacker News story identifier, shared across matching keywords.
    例45751400
  • Titletitlestring
    Story title; empty when unavailable.
    例Uv is the best thing to happen to the Python ecosystem in a decade

サンプルデータ

output.schema から生成したサンプルです。サンプル値のないフィールドには構造上のプレースホルダーを使用しています。

output.example
{
  "id": "759cbfc402d5206e48b00a01788e8f5af14e87a83916eb4f340586d316485a0e",
  "keyword": "python",
  "story_id": "45751400",
  "title": "Uv is the best thing to happen to the Python ecosystem in a decade",
  "url": "https://emily.space/posts/251023-uv",
  "hn_url": "https://news.ycombinator.com/item?id=45751400",
  "author": "todsacerdoti",
  "points": 2214,
  "num_comments": 1324,
  "created_at": "2025-10-29T18:57:29Z",
  "story_text": "<story_text>"
}

連携方法

この App は MCP、API、SDK、ファイルエクスポートのいずれでも連携でき、どのチャネルも同じ能力と料金を共有します。すべてのリクエストは Authorization: Bearer ヘッダーで認証し、認証情報には API Key(長期有効。Data Hub コンソールで作成)を使用します。MCP クライアントは OAuth によるキー不要のログインにも対応しています。CLI や Skill など、さらに多くの連携方法も準備中です。 この App は非同期で実行され、途中でキャンセルできます:キャンセル後、実行は停止します。納品済みのレコードは保持され、課金対象になります。

MCP(Model Context Protocol)を使うと、Claude や Cursor などの AI クライアントからこの App を直接呼び出せます。クライアントと認証方式を選び、下の設定をコピーしてください。

クライアント設定

Bearer の後の値を長期有効な API Key に置き換えてください。あらゆるクライアント、CI、ヘッドレス環境で利用できます。

mcpServers config
{
  "mcpServers": {
    "octoparse_datahub": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=donglichun/hacker-news-keyword-search",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}

AI に設定を任せる

設定を手作業で編集したくない場合は、インストールプロンプトをコピーして任意の AI クライアントに貼り付けてください。AI が自分のやり方でセットアップを完了します(デフォルトではログインを案内し、API Key をチャットに送るよう求めることはありません)。

detail.access.mcp.composeHint

料金

Per record returned

正常に返されたレコードの件数に応じて課金されます。失敗した実行には課金されません。

$0.0005/ 件

複数の課金イベントはそれぞれ独立して累計されます。詳細は各項目をご覧ください。失敗した実行には課金されません。

Credits を確認

今すぐ試す

パラメータを入力して実行してください。結果は実際の呼び出しによるものです。

サンプル
パラメータは送信前に input.schema で検証されます
$0.0005 / 件