Boolsai Grep
Parallel regex across all Boolsai scans — discover new vendor patterns, niche signals.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only
What it can do
What data it sees
Do you need an account
No: the server works without sign-in
Parallel regex across all Boolsai scans — discover new vendor patterns, niche signals. 4 tools.
Server tool list (4)
Raw names from tools/list. Only developers need these.
| grep_pattern | Run a JavaScript regex across every scan we've ever taken. Returns matching site URLs (and optional snippets). Best for ad-hoc discovery of patterns NOT already extracted into id_index. Pass narrowing filters (vendor, tld, since) to keep scan volume manageable. Default returns URLs only — set with_snippets=true if you also want the matched JSON context. |
| count_pattern | Same as grep_pattern but returns only the count of matching sites. Faster — no per-match serialization. Useful for sizing 'how many sites use X' before doing a full grep. |
| sites_with_signal | Return sites that have a known signal_type=signal_value pair in id_index. MUCH faster than grep_pattern — uses pre-indexed D1 lookup. Use this whenever the signal_type is in the list (see instructions). Examples: sites_with_signal(signal_type='vendor', signal_value='mparticle_workspace') ← won't work, that's an ID type, use sites_with_signal(signal_type='mparticle_workspace') WITHOUT signal_value to list all values + their domains. |
| list_signal_types | Returns the full catalog of signal_types currently present in id_index, with counts of unique values and unique domains for each. |