Bing Web Search API
Browse all Bing APIs★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey1 EndpointsREST
For Agents
Look up archived Bing Web Search response shapes when migrating an agent from the retired Bing Web Search v7 API to a replacement search provider. Single /search endpoint, Ocp-Apim-Subscription-Key authentication.
Use for: Retrieve the response schema Bing Web Search returned for a given query, Check whether the /search endpoint accepted a count or offset parameter, Find the exact authentication header Bing Web Search expected, List all answer types Bing returned alongside webpage results
Not supported: Does not handle live web queries, image search, news search, or video search — the Bing Web Search APIs were retired on August 11, 2025, and this spec is a migration reference only.
Jentic publishes the only available OpenAPI specification for Bing Web Search API, keeping it validated and agent-ready. The Bing Web Search API was Microsoft's hosted query interface that returned web pages, images, news, videos, and related entities for a single search term. The public Bing Search APIs were retired by Microsoft on August 11, 2025, so this spec is preserved for archival and migration reference. The single /search endpoint accepted a query string and a Subscription-Key header, returning ranked webpage results with snippets, deep links, and related answer types.
Install Jentic One Beta
Connect the Bing Web Search API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bing Web Search API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Bing Web Search API.
Submit a query string to the /search endpoint and parse the ranked webPages.value list
Inspect the historical response schema for migration to alternative search APIs after the August 2025 Bing retirement
Reference the Ocp-Apim-Subscription-Key header authentication pattern when porting code to a successor provider
Map Bing answer types (webPages, images, news, videos, relatedSearches) to equivalent fields in another search API
Preserve agent code paths that previously called Bing Web Search v7 for compatibility testing
Use Cases
Patterns agents use Bing Web Search API for, with concrete tasks.
★ Migration reference for retired Bing Web Search
Microsoft retired the public Bing Web Search APIs on August 11, 2025, leaving teams that depended on the v7 /search endpoint without a vendor-supplied spec. This archived OpenAPI document captures the request and response shape so engineering teams can map their existing Bing integration onto a successor provider such as Brave Search or SerpApi. Migration usually completes in a day once the response field mapping is documented.
Compare the historical Bing /search response (webPages.value[].url) with Brave Search /web/search results (web.results[].url) and produce a field mapping document
Compatibility testing for legacy agents
Some production agents still contain code paths that invoke Bing Web Search v7. This spec lets QA teams generate mock responses that match the original schema so legacy code can be exercised in isolation before the Bing call sites are removed. The /search endpoint signature, query parameter set, and webPages.value response array are all preserved verbatim from the retired Microsoft documentation.
Generate a mock /search response containing three webPages.value entries with name, url, and snippet fields matching the archived Bing schema
Agent integration via Jentic for archived spec discovery
An AI agent looking up the Bing Web Search response shape for a migration project can call Jentic with the intent 'look up archived Bing web search schema' and receive the full operation contract. Jentic returns the input schema, response schema, and the explicit retirement notice so the agent does not attempt to invoke the live endpoint. This avoids the failed-call latency that would otherwise occur when the agent hits a 404.
Search Jentic for 'archived bing web search schema', load the response schema, and return the field list to the migration planner
Key Endpoints
1 endpoints — jentic publishes the only available openapi specification for bing web search api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/search
Return ranked search results for a query (retired August 2025)
GET
/search
Return ranked search results for a query (retired August 2025)
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Bing subscription keys (now defunct) were stored encrypted in the Jentic vault and injected into the Ocp-Apim-Subscription-Key header at execution time. Agents never received the raw key.
Intent-based discovery
Agents searching Jentic for 'archived web search schema' or 'bing search response shape' surface this operation with its retirement metadata, so the agent does not attempt a live call.
Time to first call
Direct migration off Bing Web Search: 1-3 days to map response fields, swap auth, and re-test. Through Jentic with this archived spec plus a live successor schema: under 2 hours.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Bing Web Search API through Jentic.
Why is there no official OpenAPI spec for Bing Web Search API?
Microsoft does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Bing Web Search API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
Is the Bing Web Search API still operational?
No. Microsoft retired all public Bing Search APIs on August 11, 2025. The /search endpoint at api.bing.microsoft.com/v7.0/search no longer accepts requests. This OpenAPI document is preserved as a migration and archival reference only.
What authentication did the Bing Web Search API use?
Bing Web Search v7 used an apiKey scheme. Calls passed the subscription key in the Ocp-Apim-Subscription-Key header. Through Jentic the credential was stored encrypted in the vault and never appeared in agent context.
Can I still call the /search endpoint through Jentic?
No. Jentic's tool registry returns the schema for reference and migration planning, but execution attempts against api.bing.microsoft.com/v7.0/search return the same 404 the live endpoint produces. Use this spec to migrate to an active search provider.
What replaced the Bing Web Search API?
Microsoft directs former customers to Microsoft Copilot. For programmatic web search, common replacements available in Jentic include Brave Search and SerpApi. Both expose a similar query-and-results pattern that maps cleanly onto the Bing webPages.value response shape.
How do I migrate from Bing Web Search to another provider through Jentic?
Search Jentic for 'web search query' to list active providers, load the schema for the chosen replacement, and use this archived Bing spec to generate the field mapping. The webPages.value array in Bing typically maps to web.results in Brave or organic_results in SerpApi.
GET STARTED