Every unusual options print looks smart in hindsight when the stock moves your way. The harder question in real time is whether a bet is informed or just loud. One practical test: when an OptionsBell alert fires on a name that just reported, line the flow up against the actual earnings call. Does the direction of the bet match what management said, and how central were the themes the market seems to be trading? earningscalls.dev gives you both the summary and the raw mention counts to check.

Start with the alert

Say OptionsBell alerts you to a wave of put buying in a consumer name the morning after its call, short-dated, well above average premium. The market is positioned for downside. Before you assume the buyer knows something, ask what the call actually contained. If management guided down and spent the Q&A defending margins, informed put buying makes sense. If they raised guidance and the puts are still piling in, either someone disagrees loudly or the flow is a hedge, not a directional view.

Read the summary first

The AI call summary on earningscalls.dev is the fastest way to get the shape of the call: the headline numbers, the guidance change, and the two or three things analysts fixated on. That alone usually tells you whether the flow direction is consistent with the message. Then you go deeper only where it matters.

Puts + soft guidance + margin questions = flow and call agree
Calls + guide-up + buyback talk = flow and call agree
Flow that fights the call = a disagreement or a hedge, treat with caution

Use mention counts as a heat map

Summaries tell you the narrative; mention counts tell you where the pressure was. earningscalls.dev can count how often a ticker or a topic came up on a call, which turns vague impressions into something you can compare quarter over quarter. If guidance came up 14 times, AI 20 times, and buyback not at all, you know exactly what the call was really about, and whether the flow is trading the same theme.

With the earningscalls.dev MCP server in Claude, you can ask for this directly.

For $TICKER's latest earnings call, count how many times
each of these came up: guidance, demand, AI, buyback, margins.
Then give me a two-line summary of the guidance change.

A put-heavy flow print reads very differently when the call mentioned margins 18 times and demand twice. The market may be trading exactly the pressure point the call revealed.

A worked example

OptionsBell flags unusual call buying in a semiconductor name an hour after the print. You pull the summary: revenue beat, guidance raised, and AI mentioned more than 25 times against a handful last quarter. The mention count confirms the narrative shifted hard toward AI demand, and the call flow is trading straight into it. That is an informed-looking bet with the call as corroboration, not a blind chase.

Flip it: calls light up, but the summary shows in-line numbers, flat guidance, and AI mentions actually falling versus last quarter. Now the flow is running ahead of anything management said. That is the moment to size down or wait.

Turning it into a habit

The routine is short enough to run on every earnings-driven alert: read the OptionsBell print, pull the summary, glance at the mention counts for the themes you care about, then decide if the flow and the call tell the same story. It will not tell you the future, but it reliably separates bets that are anchored to the actual call from ones that are just noise around it.

Set the trigger side up first: create an unusual options activity alert, and keep earningscalls.dev ready to fact-check every print against the call.