Detect Apisearch

PluginView evaluates public page signals in these classes when identifying Apisearch. Individual fingerprint rule bodies are proprietary and are not published.

• Script sources

Illustrative indicators derived from public catalog metadata for Apisearch. A live scan may match additional proprietary rules beyond these examples.

• static.apisearch.cloud

Establishes

One or more public signals on the scanned page matched a known Apisearch signature (1 rules) at the time of the scan.

Does not establish

A sitewide install of Apisearch, an active vendor contract, exclusive use, or that Apisearch is still in place today.

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Apisearch signals.
2. 2. PluginView reads only public responses (script sources) and scores them against the Apisearch signature set (1 rules).
3. 3. Review the confidence score and text explanation for Apisearch on the results page.

Can PluginView detect Apisearch without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Apisearch — typically script sources. It does not bypass authentication or paywalls.

What category is Apisearch?

Apisearch is classified under Search engines in the PluginView directory.

How many fingerprint rules cover Apisearch?

This reference currently tracks 1 fingerprint rule across script sources. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Apisearch?

Illustrative public indicators for Apisearch include static.apisearch.cloud. A live scan may match additional proprietary rules beyond these examples.