We just added Python code to use the Intelligence X API! You can find the code in the SDK at https://github.com/IntelligenceX/SDK.
The code comes with a default API key so you can get started right away. For details on usage please look at the readme file in the SDK.
The SDK already has code implementations in HTML, PHP, and Go. It also features a command-line program written in Go, and can be compiled on Windows/Linux/Mac. The Python reference implementation is the latest addition to help developers integrate our search engine and our special Phonebook feature.
There are 2 scripts included in the SDK:
ix_search.py <selector>
ix_phonebook.py <selector>
The first script “ix_search.py” looks for any selectors, and returns all results that contain the selector. Each result has a unique “systemid” that can be used to query the actual data (note that the source data could be anything from a HTML document, a text file, a Word document, a PDF, etc.).
The second script “ix_phonebook.py” makes a phonebook lookup, i.e. it lists all selectors known for the search term. In the example below, it lists known email addresses, URLs, and domains belonging to facebook.com.
At Intelligence X we categorize data sources into buckets. Buckets can be used as filters and to broadly identify the source of individual search results. For example, the bucket “Darknet Tor” indicates the result origins from some a Tor hidden service (.onion domain) and was collected by our Tor crawler. Buckets have human readable names
We just added support for an additional 152 top-level domains (TLDs), increasing the support to 511 TLDs in total. Support means that you can search for those domains across intelx.io and APIs, and internally that our backend supports processing them. While you can start searching for them immediately, it will take some time until our
Earlier today at 11:24 The Guardian Journalist Shaun Walker posted the security procedure and the security token used to pass makeshift checkpoints in Ukraine related to the Russian Ukrainian war: This is a reminder to journalists – and the public – to take OPSEC (operations security) seriously and not endanger people on the ground. Posting