Microsoft's Bing Visual Search tool, presented as a seamless way to find similar images and related information, appears to be a complex assembly of disparate systems. Users attempting to interact with its underlying capabilities via API have encountered significant discrepancies, suggesting that the public-facing website and the developer-accessible services may not be synchronized.
The core issue identified by users is that the results provided by the bing.com/visualsearch website are frequently more precise and of higher quality than those returned by the official Bing Visual Search API endpoint (api.bing.microsoft.com/v7.0/images/visualsearch). This divergence raises questions about the underlying architecture and whether Microsoft employs different versions or configurations of its visual search technology for its own platform versus its external developer offerings.
API Limitations and User Frustration
Developers seeking granular control over Bing Visual Search functionalities have run into several roadblocks.
Read More: CPU, GPU, TPU tasks overlap, new data shows
One user's attempt to exclusively filter for 'ProductVisualSearch' results from a specified website was met with a definitive "No," indicating a lack of such precise filtering capabilities within the Bing Visual Search service. This suggests a one-size-fits-all approach for programmatic access, which may not cater to specialized search needs.
Inquiries regarding the ability to process multiple images within a single transaction for the Bing Visual Search API have also surfaced, pointing to potential limitations in handling batch requests efficiently.
A developer encountered a '401 Client Error: PermissionDenied' when attempting to call the Bing API from an application script, highlighting potential authentication and authorization complexities that users may face.
Evolving Search Paradigms
Beyond the specific issues with visual search, broader trends in search technology are also evident.
Within the development environment of Visual Studio 2019, there's an option to change the default search engine, allowing users to switch from Bing to Google for text-based searches within the IDE. This reflects a user-driven preference for customized search experiences.
In a separate context, developers have explored workarounds to prevent the appearance of a "stupid visual search icon" on images when using Microsoft Edge. This suggests an ongoing effort to manage and control the user interface elements associated with image interactions, even at the browser level.
The disparate nature of these observations—ranging from API result quality to UI integration and search engine customization—paints a picture of a search ecosystem in constant flux, where public-facing features and underlying developer tools are not always in perfect alignment.