AI discovery — why posts arrive pre-analyzed
Posts arrive already read. The moment Huntit finds a new one, an automatic pass called AI discovery watches it and fills in a set of descriptive fields — what the post is, what it contains, how it opens and closes.
You never press a button for this, and it runs on every profile you track: your client's own brand, a competitor, an inspiration profile alike. By the time a post shows up in your feed it's already labelled and searchable.
One thing is left out on purpose: a video longer than 5 minutes is never sent to the AI. It is still collected, tracked and badged like any other post — it simply arrives without AI fields, and says so.
What it reads — and what it never touches
AI discovery answers one question: what is this post, and what's in it?
It classifies the post's content group and type, writes a plain summary, names the viewer payoff, says how a video was filmed, and pulls out the hook, the outro and the transcript. Full detail on each field is in the AI-discovery fields.
It's an extractor, not a critic. It describes what's there and never rates a post, predicts whether it will perform, or tells you what to do about it.
The numbers on a post — views, likes, comments — come from tracking, not from the AI. The AI reads the content; it never sets or changes a metric.
Huntit reads only what is public. There is no login to anyone's account, no connection, nothing the tracked account can see.
The status you might see
While a discovery pass is still running, a post shows a brief Analyzing post… state. When it settles, the field set lands in one of three ways:
- Success — every field was read.
- Partial — some fields were read, others came back empty.
- Failed — the read didn't complete. In your lists that post reads "Not analyzed — the AI couldn't read this post."
Open a failed post and it names the reason on its own card.
A Re-analyze button sits on three reasons: content the provider flagged as sensitive, a technical miss, and a file the provider refused. A firm content block, or media the AI can't take, can't be changed by a re-run, so no button appears.
See when an analysis fails for each card and what to do with it.
Re-analyze usually runs the read again from the copy Huntit already stored, with no new scrape. The fields fill in for your whole team once it lands.
The one exception is a YouTube post whose file was refused: Re-analyze fetches a fresh copy of the video first, which costs a little on your Apify account.
A single — in any field is an honest empty, not an error — it means there was nothing to extract there (a silent video has no transcript; a post with no clear payoff has no value proposition). The post itself is always kept, analyzed or not.