Not a keyword alert, and not a thin wrapper around one API call. Every scan walks a multi-stage pipeline that spends the cheap passes first and the expensive ones only on what survives.
What each layer guarantees. The core is described by what it produces, not by how it works — that part stays ours.
Today that's the web app. The same engine is being kept behind a clean internal boundary so it can be exposed directly — as an API and webhooks — without rebuilding what sits underneath it.
Account isolation, plan limits and run validation all happen before any work is scheduled. One account's scans can never see, starve or bill another's.
Scans are queued rather than run inline, claimed by workers that can be scaled horizontally, and made safe to retry. A crashed worker resumes rather than losing or duplicating a run.
One connector per network, each normalising into a single internal shape. The core never learns which platform a post came from, so adding a network is a connector, not a rewrite.
The part we don't document. It decides which posts carry real buying intent, what they score and why, and what a genuinely useful reply would look like. What it produces is visible in the product; how it gets there isn't published.
Dedup memory, scored leads and full run history are held per product. The same post never reaches you twice, and every scan stays separately inspectable instead of collapsing into one feed.
The engine was deliberately kept behind a service boundary rather than wired into the interface. The dashboard is one consumer of it — the same intent scoring and response drafting is intended to be available directly, for teams who want it inside their own CRM, workflow or product.
Prefer email? support@intenthunt.io
The constraints that shaped the pipeline — and the failure modes they exist to avoid.
Scoring every result properly would be slow and costly, so the pipeline spends the cheapest possible check first and only pays for a full fetch and deep read on what survives. That ordering is the reason a scan lands in about a minute instead of ten.
There is no posting integration, and we never hold your Reddit, LinkedIn or X credentials. Replies are drafted; you open the thread and post in your own account, or you don't. That constraint is deliberate — automated replies get accounts banned and communities poisoned.
A number on its own is unfalsifiable. Each score ships with a one-line justification, so when the model is wrong you can see why it was wrong and stop trusting that pattern, instead of quietly losing faith in the whole list.
Dedup happens per product and persists across scans. The failure mode for a tool like this is re-surfacing the same twenty threads every morning until you stop opening it.
Add a description and watch the pipeline work. First results land in about a minute.
Start freeNo credit card required · see the features