logo
DE

Hacker News Keyword Search

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

Entwickler
Preise
0,0005 $ / Datensatz
Zuletzt aktualisiert
2026-11-11

Übersicht

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.

Anwendungsbereich & Grenzen

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.

  • Geeignet für
  • 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.
  • Nicht verwenden für
  • 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.

Fehlerbehandlung

Vom Entwickler deklariertes Fehler- und Wiederholungsverhalten. Wir empfehlen, es bei der Integration in Ihren System-Prompt aufzunehmen.

  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.

Eingabe

Parameter, die zum Aufruf dieser App erforderlich sind, generiert aus dem input.schema in der manifest.json.

  • KeywordskeywordsErforderlicharray<string>
    Search each string independently. Supply 1 to 20 non-empty strings; repeated identical keywords are processed once.
    Anzahlbis zu 20 EinträgeBeispiel["python"]
  • Limit per keywordlimit_per_keywordOptionalinteger
    Maximum stories returned for each keyword, from 1 to 1,000; defaults to 100. Searches with fewer available matches return fewer stories.
    Bereich1–1000Standard100
  • Sort ordersort_byOptionalstring(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.
    Zulässige WerteMost relevantrelevanceNewest firstnewestOldest firstoldestHottest (points, then comments)hottestStandardrelevance
  • Time rangetime_rangeOptionalstring(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.
    Zulässige WerteAll timeallPast 24 hourslast_24hPast 7 dayslast_7dPast 30 dayslast_30dPast 365 dayslast_yearStandardall
  • Custom date rangedate_rangeOptionalobject
    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.

Ausgabe

Feldstruktur eines einzelnen Datensatzes, generiert aus dem output.schema in der manifest.json.

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

Beispieldaten

Aus output.schema erzeugt. Felder ohne Beispielwert verwenden strukturelle Platzhalter.

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>"
}

Integration

Diese App kann über MCP, API, SDK oder Dateiexport integriert werden — alle Kanäle teilen sich dieselben Fähigkeiten und Preise. Jede Anfrage authentifiziert sich über den Authorization: Bearer-Header mit einem API Key (langlebig, in der Data Hub Konsole erstellt); MCP-Clients können sich zusätzlich per OAuth ohne Key anmelden. Weitere Optionen wie CLI und Skill sind in Vorbereitung. Diese App läuft asynchron und kann zwischendurch abgebrochen werden: Nach dem Abbruch stoppt der Lauf. Bereits gelieferte Datensätze bleiben erhalten und werden abgerechnet.

Über das MCP (Model Context Protocol) können Sie diese App direkt aus KI-Clients wie Claude und Cursor aufrufen. Wählen Sie Ihren Client und den Authentifizierungsmodus und kopieren Sie dann die Konfiguration unten.

Client-Konfiguration

Ersetzen Sie den Wert nach Bearer durch Ihren langlebigen API Key. Funktioniert in jedem Client, in CI und in Headless-Umgebungen.

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>" }
    }
  }
}

Lassen Sie die KI die Einrichtung übernehmen

Sie möchten Konfigurationen nicht von Hand bearbeiten? Kopieren Sie den Installations-Prompt und fügen Sie ihn in einen beliebigen KI-Client ein — er schließt die Einrichtung auf seine eigene Weise ab. (Standardmäßig führt er Sie durch die Anmeldung und fordert Sie nie auf, Ihren API Key im Chat zu senden.)

detail.access.mcp.composeHint

Preise

Per record returned

Berechnet nach der Anzahl der erfolgreich zurückgegebenen Datensätze. Fehlgeschlagene Läufe werden nicht berechnet.

0,0005 $/ Datensatz

Mehrere Abrechnungsereignisse werden unabhängig voneinander kumuliert. Details siehe jeweilige Position. Fehlgeschlagene Läufe werden nicht berechnet.

Credits ansehen

Jetzt ausprobieren

Füllen Sie die Parameter aus und starten Sie — die Ergebnisse stammen aus einem echten Aufruf.

Beispiel
Parameter werden vor dem Absenden gegen input.schema validiert
0,0005 $ / Datensatz