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
What does the risks field represent?
The Context API's risks field is an array of specific risk-factor tags observed for an IP, rather than a single composite score. Current values include AD_FRAUD, CALLBACK_PROXY, GEO_MISMATCH, LOGIN_BRUTEFORCE, TUNNEL, and WEB_SCRAPING — an IP can carry more than one, or none.
Do you have a bulk lookup endpoint?
No. Each IP must be submitted individually to the Context API.
Why does the Historical Context API return a 404 for an IP?
A 404 means no historical record was stored for that IP on the requested date — it does not mean the IP was reviewed and found clean. This can happen if the IP simply wasn't tracked on that date, or if the date falls outside the historical retention window (approximately the past 2 years). The non-historical Context API has broader coverage for IPs without a historical record.
Does the Context API offer historical search?
Enterprise API subscriptions can add historical lookups to their API subscription. Contact your Spur sales rep or sales@spur.us to add this.
How far back does the Historical Context API go?
The Historical Context API covers approximately the past 2 years of data, available as an add-on subscription on Enterprise plans.
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.