Bing Web Search API

Name: Bing Web Search API
Brand: Bing Web Search API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey1 EndpointsREST

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.

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 | sh

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 instance

Jentic 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

GET STARTED

Start building with Bing Web Search API

Explore with Jentic

View OpenAPI Document

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.

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

The former Bing subscription key would be stored once, encrypted, by your own Jentic One instance and injected into the Ocp-Apim-Subscription-Key header at execution time. It never enters the agent's prompt, logs, or context, though the endpoint is no longer live.

Intent-based discovery

Agents search Jentic by intent such as 'archived web search response shape', and Jentic returns the Bing /search operation with its input schema and retirement metadata so the agent reads the reference without attempting a live call.

Time to first call

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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Bing Web Search API?

Yes. Because Jentic One runs self-hosted on your own infrastructure, your rules decide which operations and credentials the agent may use. The Bing Web Search spec exposes only a single read operation, GET /search, so you can scope the agent to just that archived schema-reading capability and nothing more. You control which operations it may call, and since the service is retired there is no live endpoint for it to reach.