Hacker News Keyword Search
Find public Hacker News stories by keyword and publication period, ordered by relevance, date or points.
Descripción general
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.
| Keyword | Story ID | Title | Points | Comments | Published at |
|---|---|---|---|---|---|
| python | 45751400 | Uv is the best thing to happen to the Python ecosystem in a decade | 2214 | 1324 | 2025-10-29T18:57:29Z |
| python | 20915746 | Sunsetting Python 2 | 1616 | 704 | 2019-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.
Alcance y límites
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.
- Adecuada para
- 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.
- No usar para
- 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.
Gestión de fallos
Comportamiento de fallos y reintentos declarado por el desarrollador. Recomendamos incluirlo en tu prompt del sistema al integrar.
- 1For an empty result, try a broader or differently worded keyword; an empty result is valid.
- 2If search is temporarily unavailable or rate limited, retry later; earlier returned rows may remain after a failure.
- 3If the run times out, reduce the number of keywords or the per-keyword limit and retry.
- 4Repeated identical keywords are trimmed and processed once; use a list containing one string for a single search.
- 5Use valid YYYY-MM-DD dates with the start on or before the end; periods with no overlap return no stories.
- 6If oldest-first search is too broad, use a narrower publication period or more specific keywords.
Entrada
Parámetros necesarios para llamar a esta App, generados a partir del input.schema del manifest.json.
- Keywords
keywordsObligatorioarray<string>Search each string independently. Supply 1 to 20 non-empty strings; repeated identical keywords are processed once.Cantidadhasta 20 elementosEjemplo["python"] - Limit per keyword
limit_per_keywordOpcionalintegerMaximum stories returned for each keyword, from 1 to 1,000; defaults to 100. Searches with fewer available matches return fewer stories.Rango1–1000Predeterminado100 - Sort order
sort_byOpcionalstring(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.Valores permitidosMost relevantrelevanceNewest firstnewestOldest firstoldestHottest (points, then comments)hottestPredeterminadorelevance - Time range
time_rangeOpcionalstring(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.Valores permitidosAll timeallPast 24 hourslast_24hPast 7 dayslast_7dPast 30 dayslast_30dPast 365 dayslast_yearPredeterminadoall - Custom date range
date_rangeOpcionalobjectOptionally 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.
Salida
Estructura de campos de un único registro, generada a partir del output.schema del manifest.json.
- Match ID
idstringStable identifier for the exact trimmed keyword and story pair.Ejemplo759cbfc402d5206e48b00a01788e8f5af14e87a83916eb4f340586d316485a0e - Keyword
keywordstringThe trimmed search string that matched this story.Ejemplopython - Story ID
story_idstringHacker News story identifier, shared across matching keywords.Ejemplo45751400 - Title
titlestringStory title; empty when unavailable.EjemploUv is the best thing to happen to the Python ecosystem in a decade
Datos de ejemplo
Generado a partir de output.schema. Los campos sin valor de ejemplo usan marcadores de estructura.
{
"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>"
}Integración
Esta App se puede integrar mediante MCP, API, SDK o exportación de archivos — todos los canales comparten las mismas capacidades y precios. Cada solicitud se autentica con la cabecera Authorization: Bearer usando una API Key (de larga duración, creada en la consola de Data Hub); los clientes MCP también pueden iniciar sesión con OAuth sin clave. Más opciones como CLI y Skill están en camino. Esta App se ejecuta de forma asíncrona y se puede cancelar a mitad de camino: Tras la cancelación, la ejecución se detiene. Los registros ya entregados se conservan y se facturan.
Con MCP (Model Context Protocol) puedes llamar a esta App directamente desde clientes de IA como Claude y Cursor. Elige tu cliente y el modo de autenticación, y copia la configuración de abajo.
Configuración del cliente
Sustituye el valor tras Bearer por tu API Key de larga duración. Funciona en cualquier cliente, CI o entorno sin interfaz.
{
"mcpServers": {
"octoparse_datahub": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=donglichun/hacker-news-keyword-search",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Deja que la IA lo configure por ti
¿No quieres editar configuraciones a mano? Copia el prompt de instalación y pégalo en cualquier cliente de IA: completará la configuración a su manera. (De forma predeterminada te guía para iniciar sesión y nunca te pide que envíes tu API Key en el chat.)
detail.access.mcp.composeHint
Precios
Se cobra según el número de registros devueltos correctamente. Las ejecuciones fallidas no se cobran.
Los distintos eventos de facturación se acumulan de forma independiente. Consulta cada elemento para más detalles. Las ejecuciones fallidas no se cobran.
Ver créditosPruébalo ahora
Rellena los parámetros y ejecuta — los resultados provienen de una llamada real.