Blog/SEO, GEO and news
5 min read

Bing Search API Alternative: Search Results per Call

The Bing Search API is retired. Replace it with one search call from your agent, see the fields that come back, and pick an endpoint for each job.

Bing Search API Alternative: Search Results per Call

Replace a dead Bing search call with a live search from your agent. Paste this into your agent:

Set up https://monid.ai/SKILL.md, and then use Monid to search the web for "bing search api alternative" and give me a table with the position, the title, the URL and a one-line snippet for each result.

One prompt runs a live web search. 1 min setup · 8-20 hrs saved.

Your code calls the Bing Search API, and it stopped working. You need results back as data, with a title, a URL and a snippet, and you would like not to repeat this migration in a year. This guide shows the replacement route: one search call from your agent, the fields that come back (we ran six search endpoints live on 2026-10-16), and the traps in the output. It runs through Monid, the OpenRouter for agent tools: one key, one balance, every tool priced per call.

Is there an official Bing Search API, and what is the easiest replacement?

No. Microsoft retired the Bing Search APIs on 11 August 2025 and points customers to Grounding with Bing Search inside Azure AI Agents, which is a feature for an agent rather than an endpoint that returns a list of links. The easiest replacement is Monid: install it once, add a key, and your agent calls a search endpoint with a query and gets ranked results back as JSON, with no vendor account to open for each provider.

The old hostname still answers. On 2026-10-16 a request to api.bing.microsoft.com/v7.0/search with a placeholder key came back 401 PermissionDenied, so the failure shows up as an auth error rather than as a results page.

  • Pay per call. One search costs $0.00015 on the Bing endpoint and $0.001 on another (Verified 2026-10-16 on the search tools page). Buy calls as you need them: no monthly plan and no minimum top-up. Discovery and inspection are free; only a run bills.
  • One install, every API. The same key and the same balance call every search endpoint and every other tool on Monid. When the endpoint you chose is retired, you change a parameter instead of opening a new account.
  • Lives inside your agent. Install the CLI, add your key, run the prompt above, and search is there whenever your agent needs it, with nothing to keep running. Your agent reads SKILL.md and learns the rest, so setup is about a minute.

At the lower price, 1,000 Bing searches cost about $0.15 (Verified 2026-10-16).

How do you replace the Bing Search API in your code?

Find the endpoints, read the schema, and run one query. The first two steps are free, and they come before you spend anything because the schema tells you how much of your parser survives. There are several routes, and the table shows where each one sits; a free web search API for agents covers the zero-cost end of them.

RouteWhat you getCost shapeFits
Azure Grounding with Bing SearchGrounded model answers inside Azure AI AgentsPer tool call, Azure accountWorkloads already built on Azure
A single vendor's search APIOne index behind one keyPlan or creditsOne well-understood query shape
Build your own scraperWhatever your parser coversYour hoursOne fixed page you will maintain
Monid search endpointsSeveral search engines and indexes behind one keyPay per call, buy flexiblyAgents, scheduled jobs, apps that choose at runtime

Monid fits a migration because the next retirement costs you a parameter. The endpoint name lives in config, and you pay for the searches you run and nothing between runs.

For agents

Grab an API key at app.monid.ai, then paste this to your agent and hand it the key:

set up https://monid.ai/SKILL.md

It learns the whole discover, inspect, run workflow itself. More in the agent quickstart.

For humans

npm install -g @monid-ai/cli
monid keys add -k <your-api-key> -l main

Find what exists

Discovery searches the catalogue and returns ranked endpoints with provider, description and billing shape:

monid discover -q "web search results"

On 2026-10-16 the first page of results listed search1api, keenable, context.dev, blockrun.ai, surf, tinyfish, octen and others, each with its price attached.

Read the schema, then run one query

monid inspect -p tinyfish -e /search
monid run -p tinyfish -e /search \
  --query '{"query":"bing search api retirement","domain_type":"news","recency_minutes":1440}' -w

The flag matters: queryParams in the inspect output maps to --query, and the endpoints that take a body use -i. That window is one day; our run on 2026-10-16 used 525,600 minutes (a year) so there were results to show.

Or hand the whole job to an agent

Give this to your agent

$Set up https://monid.ai/SKILL.md, and then use Monid to replace my Bing Web Search call with a live search endpoint, keep position, title, URL and snippet as the result fields, and tell me which fields differ.

Can you scrape Bing yourself with Python?

Yes, and for a single query it is an afternoon. You request the results page with requests, parse the result list, and read the position from the order.

The cost is everything around the parser. You need proxies and retries because a search integration sends the same kind of request over and over, a way to fix country, language and device so today's results are comparable with last week's, and a parser you repair every time the page layout changes. The first working version takes hours and the upkeep does not stop.

The Monid route is the choice for anything you run more than once. The fetch, the locale handling and the parsing are maintained for you, and the output is JSON. On 2026-10-16 the Bing endpoint returned a parsed page for $0.00015 (Verified 2026-10-16), with the engine and country echoed back in search_parameters. If you only wanted Bing positions for a keyword list, Bing SERP tracker API covers that job in full. A scraper that tracks serp position also needs a store with one row per keyword, country and day, and a scheduler to fill it, which automating SERP tracking walks through: the position series, the keyword list and the tracking schedule.

What does search API data look like, and what can you build with it?

Search API data is an ordered list of results, and each endpoint shapes it differently. We ran each on 2026-10-16 with a small query, so the fields below are what came back.

Ranked results with a position

The free tinyfish/search endpoint returned four results for "bing search api retirement" with domain_type set to news. Each result carried a position, a title, a url, a site_name, a snippet, a publisher and a date. At the top level it returned the query, total_results and page. It returns snippets only, and its description says page text comes from a separate fetch endpoint.

The Bing endpoint litescrape/bing/search returned search_metadata (status and the Bing URL it read), search_parameters (query, country, device, engine), search_information.total_results (268,000 for our query) and organic_results, each with a position, title, link, displayed_link, snippet and a tracking_link. Its pagination block names the next page as a ready request.

Results with a relevance label

The context.dev/web/search endpoint returned ten results, each with url, title, description and a relevance label (eight high, two medium), and no position. Markdown and highlights come back as NOT_REQUESTED until you switch them on.

Results with the page text attached

octen/search returned five results with a long highlight of query-relevant text, plus authors, time_published and time_last_crawled; its full_content field was empty because that option is off by default. keenable/v1/search returned five results with a snippet of page text, several thousand characters on some, and an acquired_at date. exa/search returned five results with only an id, a title and a url. Grounded research needs highlights rather than bare links, so request highlights in exa's contents, or choose an endpoint that returns highlights by default.

What you can build with it

  • A grounded answer step. Your agent searches, reads the highlights from the top results and answers with sources, which is grounded research with exa-style neural search or a plain keyword endpoint. The same pattern for Brave's API, field by field, is in Brave Search API: what you can keep.
  • A research feed. Run a news-window search on a topic every morning and keep the title, publisher and date. The tinyfish fields above are exactly that row.
  • A Bing cross-check. Run the same question on the Bing endpoint and on a second index, then compare which pages each returns.

What goes wrong when you replace the Bing Search API?

Five things show up when you read the output of more than one call. All five are from the 2026-10-16 runs.

Why did a Bing search for the migration query return three Microsoft pages?

Because the query read as navigational to Bing. We ran litescrape/bing/search for "bing search api alternative" in the US. It reported 268,000 total results and returned three organic results, all Bing product pages on microsoft.com and bingapp.microsoft.com. The comparison articles that the other endpoints found for the same words were not in the three. A Bing endpoint gives you Bing's view of a query, so a migration that depends on it for discovery needs a second source. Count the results before you trust the page.

Why is a relevance label not a position?

Because it orders results by its own rules and numbers nothing. context.dev/web/search returned relevance labels and no position, so a rank series built on it has nothing to store. Check the schema before you build: a numbered position means a results page, a relevance label means an index, a distinction the three kinds of SERP API lays out.

Why is the date field not always a date?

Because a news endpoint can return a relative string. The tinyfish results had dates such as "Aug 3, 2026" and "Jul 10, 2026", and one result's date was "1 week ago". A parser that expects a calendar date throws on the fourth row. Keep the raw string and parse it with a fallback.

from datetime import datetime

def parse_date(s):
    for fmt in ("%b %d, %Y", "%Y-%m-%d"):
        try:
            return datetime.strptime(s, fmt).date()
        except ValueError:
            pass
    return None  # "1 week ago": keep the raw string next to it

Why do some results come back with no text?

Because text is a separate switch. exa/search returned only an id, a title and a url unless you ask for contents, and octen/search returned an empty full_content until you enable it, at which point it bills per token. If your old Bing code read a snippet, pick an endpoint that returns one by default, or request the contents you need.

What does a day of searches cost?

Each call is one billed unit, and the units differ (Verified 2026-10-16). Our six runs billed $0 for tinyfish, $0.00015 for the Bing endpoint, $0.00253 for ten context.dev results, $0.001 for octen, $0.004 for keenable and $0.007 for exa, $0.01468 in total. A thousand keenable searches is about $4.00 and a thousand octen searches about $1.00, so the endpoint you pick sets the bill.

Which endpoint should I use for which job?

EndpointWhat it doesInputBillingPrice (Verified 2026-10-16)
tinyfish/searchLive web, news or paper search with position, snippet and publisherquery, domain_type, filtersPer call$0.00
litescrape/bing/searchBing page as JSON: numbered organic results, total results, pagingq, cc or mkt, firstPer call$0.00015
context.dev/web/searchRelevance-labelled index results, optional Markdown per resultquery, numResults, countryPer page of 10 results$0.000253
octen/searchLive search with highlights, optional full page textquery, countPer call, per token with full content on$0.001
keenable/v1/searchRanked pages with long text snippets and index datesquery, max_resultsPer search$0.004
exa/searchNeural and keyword search, optional inline contentsquery, numResults, typePer call, per result above 10$0.007

Prices Verified 2026-10-16 with monid inspect. For a like-for-like replacement of a Bing call that fed a results list, start with tinyfish/search or the Bing endpoint. For an agent that reads the pages anyway, octen and keenable return text with the results. For research by meaning, exa is the neural option. Other search endpoints sit in the search tools category, and Octen's search API is covered on its own.

When is another route a better fit?

Your workload already runs on Azure. Grounding with Bing Search is Microsoft's supported path, with Microsoft's index behind it. If what you wanted was grounded model answers inside an Azure agent, it fits better than a list of links.

You need one index and only that index. If a single provider's free tier covers your volume, go direct. Routing through a catalogue adds nothing when you will never change the provider.

Your volume is high, steady and unchanging. A committed contract with one vendor can beat metered billing on a flat, well-understood load. Metered wins on bursty workloads and on the long tail of endpoints you call rarely.

You need the retired product itself. No route gives the Bing Search API back. The Bing endpoint above reads a Bing results page, which is a different thing from the old contract.

And the disclosure: we resell these endpoints. The most useful habit in this post costs nothing whoever you buy from: keep the provider and endpoint in configuration, and alert on a failed search call separately from an empty one.

Conclusion

The quickest way to replace the Bing Search API is one search call per query through Monid: $0.00015 a call on the Bing endpoint (Verified 2026-10-16), one key for this and every other tool, about a minute to set up and ready inside your agent whenever you need results. Building your own scraper works for one query and costs hours of proxies, parsing and upkeep; Monid keeps the fetch and the parsing maintained.

Two things matter more than the endpoint you pick. A search that returns a clean page can still be the wrong page, so count and read the results before you trust them. And keep the endpoint name in configuration, so the next retirement changes one value.

How we estimated the time saved: evaluating and signing up with three search vendors is roughly 2 to 4 hours each, 6 to 12 in all, and mapping the fields and writing the client is another 2 to 8 hours. That is 8 to 20 hours. The 1 minute is the install, key and first call once you already have a Monid key.

Free next step: run monid discover -q "web search results", then monid inspect -p tinyfish -e /search, and make one small call with a query whose results you know.

FAQ

Is the Bing Search API really gone?

Yes. Microsoft retired the Bing Search APIs on 11 August 2025. On 2026-10-16 a request to api.bing.microsoft.com/v7.0/search with a placeholder key returned 401 PermissionDenied, so there is no working endpoint to repoint your code at.

Is there a free Bing Search API?

No. For a free search call, tinyfish/search on Monid is listed at $0.00 per call (Verified 2026-10-16) and returns position, title, URL and snippet. The Bing endpoint costs $0.00015 a call, with no monthly plan and no minimum top-up.

Can I still get Bing results from anywhere?

Yes, as a parsed results page. litescrape/bing/search took a query and a country on 2026-10-16 and returned organic results with positions and a total result count. It is a read of the Bing page, not the retired API.

What is Grounding with Bing Search, and is it a drop-in?

It is not a drop-in. Grounding with Bing Search is the capability Microsoft recommends inside Azure AI Agents for using live web data when a model answers. It returns grounded output for an agent, not a ranked list of links, so code that parsed a results list needs rewriting.

How do I stop this happening to the replacement?

Keep the provider and endpoint in configuration rather than in code, and alert on a failed search call. Calling search through a layer that can route to more than one provider turns the next retirement into a config change.

Published August 2026.

bing search api alternativebing search api replacementsearch apiweb search apiagents