JP

Web Search Rerank

Search the web from a natural-language request and return relevance-ranked webpage results with content and source metadata

開発者
料金
$0.008 / 50 件
最終更新
2026-09-14

概要

Web research often starts with a question rather than a known page. This Data App turns a natural-language request into a relevance-ranked set of webpages, preserving the page text, concise summaries, source identity, and publication context needed for analysis.

It is useful for quickly building a research set around a company, product, topic, or event. Freshness and domain filters help focus the search, while account, organization, and search-role filters can narrow the results when those source attributes are available.

Data notes

Each row represents one webpage returned for the submitted search question. Page URL is used to identify a result and remove duplicates. The result set covers webpage records only; a separate image collection returned by the source is not included here.

Page content may be empty even when a title, snippet, or summary is available. Account name, organization name, site icon, cached URL, language, and family-friendly or navigational flags may also be unavailable for individual pages. Publication and crawl timestamps are preserved as source text without inferring a timezone.

What the results look like

Each row is one relevance-ranked webpage result.

Page URLPage titleSite namePublished atSnippet
https://www.example.com/article/123Xiaomi car delivery momentum continues to riseExample Site2026-08-05 14:23:10Xiaomi car deliveries have continued to grow.

Additional values include the full page content, summary, display and cached URLs, account and organization names, language, source identifiers, and crawl time.

Use cases

  • Build a research set for a company, product, market, or event by combining Page title, Page content, Snippet, and Summary.
  • Monitor recent coverage by pairing a Freshness filter with Published at and Last crawled at.
  • Compare source visibility by grouping results by Site name, Account name, or Organization name.
  • Preserve traceable source links by using Page URL and Display URL when reviewing or exporting results.

適用範囲と境界

Each run accepts one natural-language search request and returns up to 200 relevance-ranked webpage records in one response. Separate image results are not included.

  • 適している用途
  • When you need relevance-ranked webpage results for a natural-language research question
  • When you need webpage titles, summaries, content, source metadata, and publication timestamps in a structured result set
  • When you want to narrow web search by freshness, domains, account, organization, or search role
  • 適さない用途
  • When you need image-only results or a dedicated image search dataset
  • When you need private, login-only, or non-public webpage content

失敗時の処理

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

  1. 1If no useful webpages are returned, broaden the query or remove restrictive domain and freshness filters
  2. 2Retry later after rate limiting, temporary service unavailability, or a timeout
  3. 3If authentication fails, verify the API Key configured for the execution environment

入力

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

  • Search questionquery必須string
    The natural-language topic or question to search. Provide at least one character; clearer wording produces more focused results.
    例Xiaomi car delivery and sales performance
  • Result countcount任意integer
    The number of webpage results to request. The default is 10 and the allowed range is 1 to 200; fewer results may be available for a narrow query.
    範囲1–200デフォルト10
  • Freshness filterfreshness任意string
    Limits results by recency. Use noLimit, oneDay, oneWeek, oneMonth, oneYear, a date such as 2026-08-05, or a date range such as 2026-08-01..2026-08-31. The default is noLimit.
    デフォルトnoLimit
  • Included domainsinclude任意string
    Search only the listed domains. Separate up to 100 domain values with | or commas, using domain values supplied by the Data Hub domain list.
  • Excluded domainsexclude任意string
    Exclude the listed domains from the search. Separate up to 100 domain values with | or commas, using domain values supplied by the Data Hub domain list.
  • Account nameaccount_name任意string
    Filters results to an exact account name when the source identifies one. Leave empty to search without an account filter.
  • Organization nameoffice_name任意string
    Filters results to an exact organization name when the source identifies one. Leave empty to search without an organization filter.
  • Search rolerole_code任意string
    Uses a configured Data Hub search role, such as WEB_SEARCH. Leave empty to use the system default role.

出力

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

  • Account nameaccount_namestring
    The account name associated with the webpage when available.
    例China News Network
  • Cached page URLcached_page_urlstring
    The cached webpage URL when available.
  • Page contentcontentstring
    The webpage body content when available. It is independent from the snippet and summary and may be empty.
    例Xiaomi car deliveries have continued to grow, with stronger showroom traffic and steady delivery scheduling.
  • Last crawled atdate_last_crawledstring
    The source timestamp of the latest crawl, preserved as returned without timezone conversion.
    例2026-08-05 15:00:00

サンプルデータ

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

output.example
{
  "account_name": "China News Network",
  "cached_page_url": "<cached_page_url>",
  "content": "Xiaomi car deliveries have continued to grow, with stronger showroom traffic and steady delivery scheduling.",
  "date_last_crawled": "2026-08-05 15:00:00",
  "date_published": "2026-08-05 14:23:10",
  "display_url": "https://www.example.com/article/123",
  "id": "0",
  "is_family_friendly": false,
  "is_navigational": false,
  "language": "en",
  "name": "Xiaomi car delivery momentum continues to rise",
  "office_name": "<office_name>",
  "site_icon": "<site_icon>",
  "site_name": "Example Site",
  "snippet": "Xiaomi car deliveries have continued to grow.",
  "summary": "Xiaomi car deliveries have continued to grow, with stronger showroom traffic and steady delivery scheduling.",
  "url": "https://www.example.com/article/123"
}

連携方法

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

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=meme_today/data-hub-web-search-rerank",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}

AI に設定を任せる

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

detail.access.mcp.composeHint

料金

50 returned records

正常に返されたレコードの件数に応じて課金されます。失敗した実行には課金されません。 50 件を 1 つの課金単位とし、端数は 50 件に切り上げて課金されます。

$0.008/ 50 件

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

Credits を確認

今すぐ試す

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

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