For Agents
An agent can manage a site's Bing search presence through the Webmaster Tools API: verify sites, submit URLs for indexing, and read crawl, rank, query, and keyword statistics. The retired Bing Web Search API is available only as an archived schema for migrating off it to another search provider.
Bing's agent-facing surface is first-party search data about your own site, not live web results. Bing Webmaster Tools reports the crawl, index, and query statistics Microsoft records for sites you own, and lets an agent push new URLs into the index. The Bing Web Search API that once answered open web queries is retired, so the live value here is site management and search-performance reporting.
2 APIs across 2 product groups. All share one credential.
| I want to... | Use |
|---|---|
| Manage a site in Bing search and read its crawl, index, and query statistics | Bing Webmaster Tools API |
| Reference the request and response shape of the retired Bing Web Search v7 API | Bing Web Search API |
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bing APIs, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbing.com" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbing.com" | 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.
Once connected, ask your agent something like: “manage a site's presence in Bing search”.
Each workflow spans multiple Bing APIs. Jentic routes each operation to the right API automatically.
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Bing Webmaster Tools by hand means appending the apikey query parameter to every request against its JSON service endpoint and tracking submission quotas yourself, and the Web Search API no longer returns live results at all. Through Jentic you install once, import the descriptions from the API Directory, store the key once, and your agent calls them.
Permission scoping
The Bing Webmaster Tools API exposes site, crawl, submission, and stats operations, so a rule bounds which the agent may call: read-only stats and crawl reads without URL submission or site removal unless you add them. The archived Web Search description is read-only by nature, and you choose the allowed set for both.
Credential isolation
Your Bing Webmaster Tools key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
An agent searches Jentic by intent, for example 'submit a URL to Bing for indexing' or 'archived web search response shape', and Jentic returns the matching Bing operation with its input schema, so the agent calls the right endpoint without browsing the reference docs.
Specific to using Bing APIs through Jentic.
Can AI agents use Bing's APIs?
Yes. Both the Bing Webmaster Tools API and the archived Bing Web Search description are in the Jentic API Directory, so an agent can discover and call their operations by intent. Through Jentic the agent searches for an operation, loads its schema, and executes it. Install Jentic One (self-hosted) from https://github.com/jentic/jentic-one to get started.
Is the Bing Web Search API still available?
No. Microsoft retired all public Bing Search APIs on August 11, 2025, so the /search endpoint no longer accepts requests. Jentic keeps its OpenAPI description as an archival and migration reference: an agent can read the schema to plan a move to another search provider, but a live call still returns the same failure the endpoint now produces.
What authentication do Bing's APIs use?
Both declare apiKey authentication with separate keys. The Bing Webmaster Tools API takes a Webmaster Tools key on the apikey query parameter; the retired Web Search API expected a subscription key in the Ocp-Apim-Subscription-Key header. Through Jentic a key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.
Is there a Bing MCP server?
You don't need an MCP server to give your agent Bing Webmaster Tools. Jentic connects it directly from the API Directory: import it, store your key once, and your agent submits URLs and reads crawl and search-performance stats on demand, without loading another server's tool definitions into its context.
Can I limit what my agent is allowed to do with Bing's APIs?
Yes. Because you run Jentic One yourself, your rules decide which operations the agent may call. You can allow read-only Webmaster Tools operations such as GetCrawlStats and GetQueryStats while leaving out URL submission or site removal, and every call the agent makes is logged.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
Use for: Managing a site in Bing search and reading its crawl, index, and search-performance statistics
Not supported: Live web search, Paid search ads, Content publishing, Image or video search
Credentials: Both descriptions declare apiKey authentication, but the keys are separate products: the Bing Webmaster Tools API takes a Webmaster Tools API key on the apikey query parameter, while the retired Bing Web Search API expected a subscription key in the Ocp-Apim-Subscription-Key header. There is no single credential across the two, and the Web Search key can no longer reach a live endpoint.
Across 2 Bing APIs: 1 vendor-official, 1 Jentic-generated, all indexed by Jentic and kept validated and agent-ready.
Bing exposes two very different APIs in the Jentic API Directory. The Bing Webmaster Tools API manages how a site appears in Bing search: it verifies and manages sites, reads crawl statistics and crawl issues, submits URLs and content for indexing, and returns rank, traffic, query, page, keyword, and inbound-link data. The Bing Web Search API was Microsoft's hosted query interface that returned web pages, images, news, and videos for a search term; Microsoft retired the public Bing Search APIs on August 11, 2025, so its single /search description is preserved as a migration and archival reference only.
Migrate off Bing Web Search to first-party data
A team that relied on the retired Bing Web Search API for search results moves to Bing's own site data. The agent reads the archived Web Search response shape to understand what its old integration expected, then pulls rank-and-traffic, query, and page statistics from Bing Webmaster Tools so reporting keeps running on first-party data instead of the dead search endpoint.
Load the archived /search response schema, then call GetRankAndTrafficStats and GetQueryStats on the site to rebuild the reporting the retired search API used to feed.
Bing Web Search API + Bing Webmaster Tools API
Plan a search-provider migration with a field mapping
Before removing Bing Web Search call sites, an agent documents the change. It reads the archived /search request and response schema to capture the fields the old code consumed, and lists the Bing Webmaster Tools query and keyword operations to confirm which first-party signals Bing still offers, so the migration plan names an exact replacement for each field.
Read the /search schema field list, list the GetQueryStats and GetKeywordStats outputs, and produce a field mapping from the retired search response to available Bing data.
Bing Web Search API + Bing Webmaster Tools API
What replaced the Bing Web Search API, and how do I migrate?
Microsoft points former customers to Microsoft Copilot, and for programmatic search common replacements in the Jentic API Directory include Brave Search and SerpApi. Read the archived Bing /search schema to capture the fields your code used, then map them onto the replacement provider's response while pulling first-party performance data from Bing Webmaster Tools.
All 3 are in the Jentic catalogue with the same one-credential, intent-search pattern.