MCP + API · kestrel/bing-web-search

Bing Search - Web Results, URLs & Snippets

Search Bing in batches by query and market. One row per organic web result: title, destination URL, domain, snippet, page and position. Filter text or domains; skip saved IDs or unchanged hashes. JSON for research agents. Public snippets only, not fetched article bodies.

Open Actor Download MCP config

Connect this tool

Add this URL as a remote MCP server in your client, then sign in to Apify. For a client-specific setup, use Apify's configurator.

https://mcp.apify.com?tools=call-actor,fetch-actor-details,kestrel/bing-web-search
Generic MCP client configuration
{
  "mcpServers": {
    "kestrel-bing-web-search": {
      "url": "https://mcp.apify.com?tools=call-actor,fetch-actor-details,kestrel/bing-web-search"
    }
  }
}

Understand the output before you run

Declared dataset fields and row types · Output locations and dataset links

Use the declared dataset schema for item fields; the output schema describes where results are stored. Optional fields may be null or absent. If an integration shows a sampled schema without an optional field, check this declaration, the Actor instructions and actual returned rows before concluding that the field is unsupported.

Inspect 12 declared output fields
FieldTypeMeaning
idstring / null
typestring / null
titlestring / null
querystring / null
urlstring / null
domainstring / null
snippetstring / null
pagenumber / null
positionnumber / null
source_urlstring / null
content_hashstring / null
fetched_atstring / null

Read an observed output example and its input, observation date and limits. These are historical source values, not a current quote or a promise of the same result.

Start with a small sample

Use call-actor with the JSON below. The $0.25 run ceiling is separate from the Actor input and may stop the sample early. Change the target to match your request. This input validates against build 1.0.4; it is not a promise that the source has matching rows today.

{
  "actor": "kestrel/bing-web-search",
  "input": {
    "queries": [
      "project management software"
    ],
    "maxResults": 3,
    "maxPagesPerSource": 1
  },
  "callOptions": {
    "maxTotalChargeUsd": 0.25,
    "timeout": 300
  },
  "waitSecs": 30
}

After completion, use get-dataset-items with storages.datasets.default.id. If still running, poll get-actor-run using the returned runId. Check status rows and errors before treating an empty dataset as no matches.

Call from Python, JavaScript or REST

Python SDK 3 example · JavaScript SDK 2 example · curl + jq example. Each uses this same small input, reads APIFY_TOKEN from your environment, sets a five-minute run timeout and exports all dataset row types as JSON Lines. The $0.25 run ceiling is separate from the Actor input and may stop the sample early. Inspect the run and source status before treating results as complete. Installation and usage.

Pricing and limits

Current listed event prices in USD. Some Actors charge for successful source checks even when no output rows match. The event descriptions below define those differences.

EventUSD eachWhat is charged
page-parsed$0.004One successfully parsed source result page, $4 per 1,000 pages. Paid even when filters, exclusions or a recognized empty result leave zero rows. Source bootstrap/sort reads are included. Failed or blocked responses are not charged. No start fee; proxy and compute are included. See maxPagesPerSource; maxTotalChargeUsd is an Apify run option.
result$0.001One delivered result with row keys title, url, domain, snippet, page, position. $1 per 1,000 rows, plus the separate parsed-page fee. Filtered, duplicate and excluded rows are not charged for the row event. No start fee; proxy and compute are included. Collection stops when the maxTotalChargeUsd run option cannot cover another page and row.

Contracts for agents

Public contract checked 2026-11-11. Active build: 1.0.4. Refresh live details before a large or recurring run.