EN

Data Hub Content Search

Search Data Hub content with a phrase and filters, then return matching page records with source metadata and content text.

Developer
Pricing
$0.005 / 20 records
Last updated
2026-09-14

Overview

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 IDContent titleSource sitePublication timeContent textOriginal URL
0小米汽车交付节奏持续提升Example Site2026-08-16 14:23:10小米汽车近期交付节奏持续提升。数据显示,相关门店试驾热度上升,交付安排正在稳步推进。https://www.example.com/article/123
1新能源汽车销量观察Industry News2026-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.

Scope and boundaries

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.

  • Good for
  • 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.
  • Do not use for
  • 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.

Failure handling

Failure and retry behavior declared by the developer. We recommend including it in your system prompt when integrating.

  1. 1An empty result list means that no content matched the phrase and filters; broaden the phrase or remove a restrictive filter.
  2. 2For authentication or authorization errors, verify the API Key configured for the execution environment before retrying.
  3. 3For rate-limit or temporary service errors, retry later without changing the search unless the error persists.

Input

Parameters required to call this App, generated from the input.schema in manifest.json.

  • Search phrasekeywordRequiredstring
    Required complete phrase matched against content titles and summaries. Do not leave it empty.
    Exampleiphone
  • Publication time rangefreshnessOptionalstring
    Limit 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.
    DefaultnoLimit
  • Included domainsincludeOptionalstring
    Only return results from these domains. Separate multiple domains with | or ,; leave empty to include all domains.
  • Excluded domainsexcludeOptionalstring
    Exclude results from these domains. Separate multiple domains with | or ,; leave empty to exclude none.
  • Account nameaccount_nameOptionalstring
    Filter for an exact content account name; leave empty to use no account filter.
  • Organization nameoffice_nameOptionalstring
    Filter for an exact organization name; leave empty to use no organization filter.
  • Result pagepageOptionalinteger
    Page 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.
    Range1–50Default1
  • Sort fieldsort_fieldOptionalstring(enum)
    Field used to order results. The default publishTime shows the newest published content first when paired with the default descending order.
    Allowed valuespublishTimecrawlerTimeidcleanUpdateTimeDefaultpublishTime
  • Sort directionsort_orderOptionalstring(enum)
    Use ascending or descending order for the selected sort field. The default desc returns the newest or largest values first.
    Allowed valuesascdescDefaultdesc

Output

Field structure of a single record, generated from the output.schema in manifest.json.

  • Account nameaccount_namestring
    Name of the account associated with the content; may be null when the source does not provide one.
    ExampleChina News Network
  • Cached page URLcached_page_urlstring
    URL of a cached version of the page when available; the source may return null.
  • Content textcontentstring
    Full content text when available. It is independent from snippet and summary and may be null.
    Example小米汽车近期交付节奏持续提升。数据显示,相关门店试驾热度上升,交付安排正在稳步推进。
  • Last crawled timedate_last_crawledstring
    Most recent crawl timestamp in the source format; may be null.
    Example2026-08-17 09:12:30

Sample data

Generated from output.schema. Fields without a sample value use structural placeholders.

output.example
{
  "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

This App can be integrated via MCP, API, SDK, or file export. All channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API key (long-lived, created in the Data Hub Console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way.

With the MCP (Model Context Protocol), you can call this App directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.

Client config

Replace the value after Bearer with your long-lived API key. Works in any client, CI, or headless environment.

mcpServers config
{
  "mcpServers": {
    "octoparse_datahub": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=meme_today/data-hub-content-search",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}

Let AI set it up for you

Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client. It will complete the setup its own way. (By default it guides you through signing in, and never asks you to send your API key in the chat.)

detail.access.mcp.composeHint

Pricing

per 20 returned records

Charged by the number of records successfully returned. Failed runs are not charged. Billed in units of 20 records; any partial unit is rounded up to 20 records.

$0.005/ 20 records

Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.

View credits

Try it now

Fill in the parameters and run. Results come from a real call.

Example
Parameters are validated against input.schema before submission
$0.005 / 20 records