Products
Investigation console
One black workspace for search, profiles, breaches, maps, tools, tickets, and history — the surface investigators actually live in.
Overview
How this surface runs.
Inquire’s console streams module results as they finish, keeps Discord and Steam profile cards readable, and stores history so you can reopen a case without reconstructing it from memory.
Notes, exports, and team folders sit beside the same session. No tab chaos.
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 — Console
Everything in one seat
Modules, API keys, settings, and investigations share the same authenticated session — so enrichment and case work never diverge.
Start from email, phone, username, Discord, Steam, domain, IP, or image. Format detection routes the right packs; you can also pin a module explicitly.
- Dark, serious UI built for long sessions
- Strong vs weak match clarity
- Empty shells filtered from view
02 — Results
Readable cards, not JSON walls
Profile and breach sections are structured for humans first. Gaming and chat lattices become cards you can brief from.
03 — Continuity
Come back tomorrow
History preserves timestamps, filters, and coverage so the next shift inherits the case — not a blank search box.
The product investigators open every day
If you only ever use one Inquire surface, make it the console — then grow into the API when automation matters.
Ready to investigate
Open the console or call the API — same modules, live results, black-and-white clarity.