Insights
Our investigation method
How Inquire turns a selector into a defensible narrative: stream first, correlate second, export last — and keep the dead ends visible.
Overview
How this surface runs.
We design for investigators who must explain their work. That means labeled sources, timestamps, and the courage to show empty modules.
The console and API share one method so automation never invents a second story.
What this surface actually returns.
The list below is the short version. Each item maps to a module or a control that exists in the console today.
01 — Method
Dead ends included
Like our case studies, we show empty lanes — so you trust the hits that remain.
A finding is stronger when you can see what was tried and failed. Inquire keeps that path in history.
02 — Correlate
Presence vs exposure
We deliberately separate accounts that exist today from credentials that leaked before — the mistake that wrecks briefings.
03 — Ship
Human and machine parity
Whatever you automate through the API should match what an analyst sees in the console.
Ready to investigate
Open the console or call the API — same modules, live results, black-and-white clarity.