Bing Search APIs: retired on August 11, 2025

Microsoft retired the public Bing Search and Bing Custom Search APIs on August 11, 2025. Which APIs went, what happened to existing keys and what Microsoft points to now.

Short answer

Bing search integrations can no longer use the retired public Bing Search or Bing Custom Search APIs, including existing instances. Microsoft directs new work to Grounding with Bing Search, a tool for Azure AI Agents.

Status checked 2026-11-12.

Routes that work for Bing data

The official route first, then the catalogue Actors that fit this problem (search results), by their published fields. Store figures are the publisher's public numbers.

Routes for Bing data
RouteCore fieldsPrice / 1KSuccess, 30 daysLink
RetiredBing Search APIs (retired)not comparedbelowOfficial docs
Bing Organic Search Results Scraper4/4$0.9915 runs, too few to rateOpen in Apify Store
Search & URL Markdown Extractor for LLMs2/4$0.99100% of 29 runsOpen in Apify Store
Google Image Search Results & Metadata Scraper3/4$0.9919 runs, too few to rateOpen in Apify Store

Official price: No public Bing Search API price is available because the product was retired. Compare all 11 Bing routes.

What is verified

FactValue
AnnouncedMay 15, 2025
RetiredAugust 11, 2025
APIs coveredWeb, Image, News, Video, Visual, Custom, Entity, Spell Check and Autosuggest search APIs
Existing instancesDecommissioned completely; no new sign-ups
Microsoft's suggestionGrounding with Bing Search, a tool for Azure AI Agents

Existing instances were decommissioned

Microsoft's retirement announcement confirms complete decommissioning and the end of new sign-ups. Keeping an existing instance or key cannot preserve access to the retired APIs.

Grounding changes the integration choice

Microsoft points to Grounding with Bing Search for Azure AI Agents. Evaluate that agent tool against the application's search requirements; an application collecting search results needs to confirm how the proposed replacement delivers the information it uses.

What works now

Microsoft's suggested route is Grounding with Bing Search for Azure AI Agents. For applications that collect search results, compare that integration model with the application's requirements before selecting it; the retired public API instances are unavailable.

Questions people ask

Will an existing Bing Search API key keep working?

Microsoft completely decommissioned existing instances. An old key cannot restore access to the retired service.

Was Bing Custom Search included?

Bing Custom Search was included in the retirement. It requires a migration alongside the other affected search APIs.

What does Microsoft recommend now?

Microsoft recommends Grounding with Bing Search. It is a tool for Azure AI Agents.

Can archived documentation restore API access?

The archived documentation describes the retired services. Use it to understand an old integration, then choose an available replacement.

Sources

Every dated claim on this page comes from the public sources below. Check the source before you make a business decision on it.

Content updated 2026-11-12Data checked 2026-11-12

Get Bing data with a catalogue Actor

Bing Organic Search Results Scraper returns 4 of 4 core Bing fields at $0.99 per 1,000 results. Compare all 11 Bing routes.

Open in Apify Store