Search the web from a natural-language request and return relevance-ranked webpage results with content and source metadata
Data Hub Content Search
Search Data Hub content with a phrase and filters, then return matching page records with source metadata and content text.
Übersicht
Data Hub Content Search turns a complete phrase into a structured page of matching content records. It brings together the result title, text, summary, source details, publication timing, and URLs so research teams can move from a topic to evidence without manually opening every search result.
The search is useful for monitoring a phrase across public content sources, collecting a reproducible result set, and comparing what different sources publish about the same topic. Filters for time, domain, account, and organization help narrow the result set to the slice that matters.
Data notes
Each record comes from the Data Hub content search index and represents one matched content result. Results are returned in the requested page order, while the search response also reports the estimated total number of matches. Some source metadata, cached links, classification flags, and full content fields can be missing, so those values may be null. The original URL, display URL, snippet, summary, and full content are separate fields and should not be treated as interchangeable.
The search matches the complete phrase against content titles and summaries. It can restrict results to included domains, remove excluded domains, and apply exact account or organization filters. The returned language and timestamps follow the source values; the API documentation does not define a common timezone for those timestamps.
What the results look like
Each row represents one content result:
| Result ID | Content title | Source site | Publication time | Content text | Original URL |
|---|---|---|---|---|---|
| 0 | 小米汽车交付节奏持续提升 | Example Site | 2026-08-16 14:23:10 | 小米汽车近期交付节奏持续提升。数据显示,相关门店试驾热度上升,交付安排正在稳步推进。 | https://www.example.com/article/123 |
| 1 | 新能源汽车销量观察 | Industry News | 2026-08-15 10:05:00 | 新能源汽车市场的月度销量变化受到多项因素影响。 | https://www.example.com/article/456 |
Additional fields include account and organization names, crawl time, language, snippets, summaries, display URLs, cached page URLs, site icons, and source classification flags.
Use cases
- For topic monitoring, compare “Content title”, “Publication time”, and “Original URL” across repeated searches to identify newly published coverage.
- For source research, group “Source site”, “Account name”, and “Organization name” to see which publishers contribute to a topic.
- For evidence review, read “Content text”, “Short snippet”, and “Content summary” together, then use “Display URL” or “Original URL” to open the source page.
Anwendungsbereich & Grenzen
Each call returns one page of up to 200 matching content records. Pages 1 through 50 can be requested, covering at most 10,000 records per search.
- Geeignet für
- When you need matching Data Hub content for a complete phrase, topic, brand, or event.
- When you need content titles, summaries, source details, publication times, and URLs for monitoring or research.
- Nicht verwenden für
- When you need more than 10,000 matches from one search.
- When you need unrestricted full-text crawling beyond the records returned by Data Hub search.
Fehlerbehandlung
Vom Entwickler deklariertes Fehler- und Wiederholungsverhalten. Wir empfehlen, es bei der Integration in Ihren System-Prompt aufzunehmen.
- 1An empty result list means that no content matched the phrase and filters; broaden the phrase or remove a restrictive filter.
- 2For authentication or authorization errors, verify the API Key configured for the execution environment before retrying.
- 3For rate-limit or temporary service errors, retry later without changing the search unless the error persists.
Eingabe
Parameter, die zum Aufruf dieser App erforderlich sind, generiert aus dem input.schema in der manifest.json.
- Search phrase
keywordErforderlichstringRequired complete phrase matched against content titles and summaries. Do not leave it empty.Beispieliphone - Publication time range
freshnessOptionalstringLimit results to a relative period such as oneMonth, a YYYY-MM-DD date, or a YYYY-MM-DD..YYYY-MM-DD date range. The default noLimit searches without a time limit.StandardnoLimit - Included domains
includeOptionalstringOnly return results from these domains. Separate multiple domains with | or ,; leave empty to include all domains. - Excluded domains
excludeOptionalstringExclude results from these domains. Separate multiple domains with | or ,; leave empty to exclude none. - Account name
account_nameOptionalstringFilter for an exact content account name; leave empty to use no account filter. - Organization name
office_nameOptionalstringFilter for an exact organization name; leave empty to use no organization filter. - Result page
pageOptionalintegerPage number to retrieve. Pages are 200 records each; page 1 is the first page and page 50 is the last page within the 10,000-record search limit.Bereich1–50Standard1 - Sort field
sort_fieldOptionalstring(enum)Field used to order results. The default publishTime shows the newest published content first when paired with the default descending order.Zulässige WertepublishTimecrawlerTimeidcleanUpdateTimeStandardpublishTime - Sort direction
sort_orderOptionalstring(enum)Use ascending or descending order for the selected sort field. The default desc returns the newest or largest values first.Zulässige WerteascdescStandarddesc
Ausgabe
Feldstruktur eines einzelnen Datensatzes, generiert aus dem output.schema in der manifest.json.
- Account name
account_namestringName of the account associated with the content; may be null when the source does not provide one.BeispielChina News Network - Cached page URL
cached_page_urlstringURL of a cached version of the page when available; the source may return null. - Content text
contentstringFull content text when available. It is independent from snippet and summary and may be null.Beispiel小米汽车近期交付节奏持续提升。数据显示,相关门店试驾热度上升,交付安排正在稳步推进。 - Last crawled time
date_last_crawledstringMost recent crawl timestamp in the source format; may be null.Beispiel2026-08-17 09:12:30
Beispieldaten
Aus output.schema erzeugt. Felder ohne Beispielwert verwenden strukturelle Platzhalter.
{
"account_name": "China News Network",
"cached_page_url": "<cached_page_url>",
"content": "小米汽车近期交付节奏持续提升。数据显示,相关门店试驾热度上升,交付安排正在稳步推进。",
"date_last_crawled": "2026-08-17 09:12:30",
"date_published": "2026-08-16 14:23:10",
"display_url": "https://www.example.com/article/123",
"id": "0",
"is_family_friendly": false,
"is_navigational": false,
"language": "zh",
"name": "小米汽车交付节奏持续提升",
"office_name": "<office_name>",
"site_icon": "<site_icon>",
"site_name": "Example Site",
"snippet": "小米汽车近期交付节奏持续提升。",
"summary": "小米汽车近期交付节奏持续提升,相关门店试驾热度上升。",
"url": "https://www.example.com/article/123"
}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.
Ü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": {
"octoparse_datahub": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=meme_today/data-hub-content-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
Berechnet nach der Anzahl der erfolgreich zurückgegebenen Datensätze. Fehlgeschlagene Läufe werden nicht berechnet. Abgerechnet in Einheiten von 20 Datensätze; jede angefangene Einheit wird auf 20 Datensätze aufgerundet.
Mehrere Abrechnungsereignisse werden unabhängig voneinander kumuliert. Details siehe jeweilige Position. Fehlgeschlagene Läufe werden nicht berechnet.
Credits ansehenJetzt ausprobieren
Füllen Sie die Parameter aus und starten Sie — die Ergebnisse stammen aus einem echten Aufruf.