A Bing Search API alternative

How they differ

Microsoft Learn: "Bing Search APIs will be retired on August 11, 2025. Any existing instances of Bing Search APIs will be decommissioned completely, and the product will no longer be available to be used or new customer signup."

Microsoft recommends Grounding with Bing Search as part of Azure AI Agents. It is a tool inside an Azure AI agent, not a search endpoint: Microsoft's documentation says developers and end users do not have access to the raw content it returns, and it needs a Grounding with Bing Search resource connected to an Azure AI project. If your code needs a list of results (title, link, snippet) to process, you need a search API instead.

CrawlerData's Google Search API returns that list as JSON from Google's results in any of 31 countries: organic results with title, link and snippet, plus AI Overview, People Also Ask, ads, the local pack and more.

One difference to plan for: the results come from Google, not Bing, so positions and snippets will differ from what your Bing integration returned. Re-baseline any stored rankings or evaluation sets.

At a glance

List prices in USD, excluding tax, as published on October 20, 2026. "Not published" means we could not find it on Bing Search API's public pages. Per-1,000 figures marked "our arithmetic" divide a plan price by its volume.

Moving from Bing Search API

The core fields carry over. webPages.value[] becomes organic_results[], name becomes title and url becomes link; snippet keeps its name. Instead of an Ocp-Apim-Subscription-Key header and query-string parameters, you send a JSON body with a Bearer token.

const url = new URL('https://api.bing.microsoft.com/v7.0/search');
url.search = new URLSearchParams({ q: 'best crm software', mkt: 'en-US', count: '10' });
const data = await (await fetch(url, { headers: { 'Ocp-Apim-Subscription-Key': API_KEY } })).json();
const results = (data.webPages?.value ?? []).map((p) => ({ title: p.name, url: p.url, snippet: p.snippet }));

const res = await fetch('https://api.crawlerdata.com/v1/jobs', {
  method: 'POST',
  headers: { Authorization: 'Bearer YOUR_API_KEY', 'Content-Type': 'application/json' },
  body: JSON.stringify({ endpoint: 'google-search', params: { query: 'best crm software', country: 'us', language: 'en' }, queue: 'live' }),
});
const { job, result } = await res.json(); // job.status "failed" => result is null, 0 credits
const results = (result?.organic_results ?? []).map((r) => ({ title: r.title, url: r.link, snippet: r.snippet }));

• link is the real destination URL, so stored URLs and deduplication keep working.
• Results are Google's public results for the query, as a searcher in the country you choose sees them. They are not Bing's, so re-baseline stored positions.
• For batches, use the fast or regular queue and receive results by webhook, at the same price as live.

Full request and response schemas are in the OpenAPI spec, with runnable code in the examples repo. AI clients can connect to the MCP server at https://api.crawlerdata.com/mcp with the same API key.

Sources

All checked on October 20, 2026 (as of Oct 2026). Spotted something out of date? Email contact@crawlerdata.com and we will correct it.

• Microsoft Learn: Bing Search APIs retiring on August 11, 2025 (learn.microsoft.com/en-us/lifecycle/announcements/bing-search-api-retirement)
• Microsoft Learn: How to use Grounding with Bing Search in Foundry Agent Service (learn.microsoft.com/en-us/azure/ai-foundry/agents/how-to/tools/bing-grounding)
• Microsoft Learn (archived): Bing Web Search API v7 endpoints (learn.microsoft.com/en-us/previous-versions/bing/search-apis/bing-web-search/reference/endpoints)
• Microsoft Learn (archived): Bing Web Search API v7 query parameters (learn.microsoft.com/en-us/previous-versions/bing/search-apis/bing-web-search/reference/query-parameters)
• Microsoft Learn (archived): Bing Web Search API v7 response objects (learn.microsoft.com/en-us/previous-versions/bing/search-apis/bing-web-search/reference/response-objects)
• CrawlerData pricing