Context API Chrome Extension
Install Spur's Context API Chrome Extension to look up IP enrichment data directly from any web page — highlight an IP and get results inline, without leaving your browser. This is a developer-mode tool, not a Chrome Web Store listing.
Difficulty
Intermediate
Some product familiarity helpful
Time estimate
5 minutes
Typical time to complete
Prerequisites
- A Spur Context API key
- Google Chrome with access to Developer Mode for extensions
What you'll achieve
- Install the Context API Chrome Extension
- Look up IP enrichment data directly from any web page
Steps
- 1
Download and load the extension
This extension is distributed as source code, not through the Chrome Web Store. Download or clone the repository from GitHub: spurintel/chrome-context. In Chrome, go to the menu (top-right) > More Tools > Extensions, then turn on Developer Mode using the toggle in the top-right of that page.
- 2
Load the unpacked extension
Click "Load unpacked" in the top-left of the Extensions page and select the extension directory from the downloaded repository. The extension icon will appear in your Chrome toolbar.
- 3
Add your Context API key
Right-click the extension icon, choose Options, and enter your Spur Context API key. The extension needs this to make enrichment requests on your behalf.
- 4
Look up an IP address
On any web page, highlight an IP address, then either click the extension icon or press Ctrl+Shift+F (the default shortcut, changeable at chrome://extensions/shortcuts). Spur's Context API enrichment data for that IP appears inline.
Related FAQs & guides
How frequently is Spur data updated?
The Context API reflects new intelligence in real time as it becomes available. Data feeds are updated daily, and organizations can also consume updates in real-time through streaming or feed-based workflows depending on operational requirements.
Can Spur enrich large volumes of IP addresses?
Yes. Organizations commonly use the Spur Context API and data feeds to enrich IP addresses at scale, enabling proxy detection, VPN identification, infrastructure classification, and geolocation analysis across large datasets.
Do you have a confidence score or last seen date?
Spur operates on a "high confidence" only model to reduce the likelihood of false positives ever making it into our data. Our mentality is that our customers should trust us to decide if something is true rather than providing an arbitrary score to constantly adjust higher or lower. Every API request or Monocle session provides the latest true information for that moment in time. On-prem solutions are updated at their purchased cadence (daily or real-time). We actively purge any result that is no longer true and maintain smart age-offs to maintain the most accurate snapshot of data each day.
Should Spur data be used as a blocking list?
Generally, no. Spur is designed to provide context and intelligence rather than a simple allow/block decision. Most organizations achieve the best results when Spur data is incorporated into broader risk models and decisioning workflows.
If Spur identifies a provider such as NetNut, does that mean the traffic originated directly from that provider's customer?
Not necessarily. Proxy ecosystems often involve resellers, downstream providers, SDK operators, and shared infrastructure. A provider label identifies infrastructure associated with the traffic but should not be treated as attribution of a specific end user without additional evidence and investigation.
Does Spur offer downloadable feeds, local deployments, or MMDB-style delivery?
Available delivery methods may vary by product and customer requirements. Organizations with low-latency or high-volume enrichment needs should contact Spur to discuss available deployment and data-delivery options.