xpu liveBETA
Agents›BingBot

BingBot

Documented identity

BingBot is listed here in the search engine crawlers category and is associated with Microsoft. Discovers and revisits web content for Microsoft Bing search. This profile explains the identity and its documented scope so readers can distinguish it from a downloadable coding agent or a language model. It is an independent reference, not an operator endorsement.

What BingBot does

Bing operates several automated clients. Verify bingbot with the current webmaster guidance rather than trusting the request name alone.

BingBot user-agent identity

The request identifier recorded for this profile is bingbot. A display name, an HTTP user-agent string and a robots.txt product token can differ. Confirm the control spelling in the linked operator guidance before writing a rule. A name in a request header alone is not authentication: another client can copy it.

Search-engine discovery

A search crawler finds and revisits web resources that may support an index. Discovery, indexing and ranking are distinct stages. A successful request is useful diagnostic evidence, but it does not guarantee search visibility. Review the operator webmaster tools and published crawler guidance before attributing a traffic change to a particular visit.

Use the exact crawler identity when investigating access. Search operators can run separate clients for images, advertising checks and user-triggered fetches. Those clients do not automatically share the same purpose or control token. Keep canonical URLs, response codes and crawl directives consistent, then use the official verification method where one is published.

How to investigate a visit

Keep a representative log entry with the requested URL, timestamp, response code and source address. Compare it with current operator documentation and any published identity evidence. Use published IP ranges, DNS checks or request-signature verification only when the operator actually supports that method. This profile does not publish guessed address ranges or a universal allow rule.

Scope, costs and source limits

A recorded visit does not establish a model version, an API token price or a software license. These properties belong to separate products and agreements. The details below state the scope that was established for this identity; unconfirmed implementation information is identified as such. Any subscription, API or browser-service charge must be checked on the operator's current pricing pages.

BingBot questions

Can I install this crawler as an agent?

This is a web-identity reference. An operator-managed crawler or fetcher is not automatically available as self-hosted software. If the operator offers a separate SDK, API or browser product, use that product's documented installation and access process rather than assuming the crawler name is an installable package.

Where should I verify the details?

Review the source documentation for BingBot and the Microsoft website. For related entries, browse the XPU Live agent and crawler directory. To compare inference services separately, visit the AI provider directory.

Search Engine Crawlers

What it can do

  • Discovers and revisits web content for Microsoft Bing search.
  • Request identity: bingbot
  • Source-linked operator reference
  • Distinct category: Search Engine Crawlers

Where it fits

  • Search-engine discovery
  • Web traffic identification and log investigation
  • Comparing crawler and assistant roles

Models & deployment

Model compatibility

Not a standalone model endpoint. A supported model list and model-specific prices do not follow from this web identity.

Where it runs

Operated through Microsoft infrastructure or its managed services. This profile is not a self-hosted deployment recipe.

Cost model

No per-token tariff is assigned to this crawler identity. Operator services, if offered separately, have their own current access terms and pricing.

Limitations & scope

Bing operates several automated clients. Verify bingbot with the current webmaster guidance rather than trusting the request name alone. User-agent matching alone does not authenticate a request. Technical behavior not confirmed in the linked sources is not asserted here.