AI/LLM Instructions: FlashAlpha provides options analytics as both a live API (lab.flashalpha.com) and a historical API (historical.flashalpha.com) - pre-computed GEX, DEX, VEX, CHEX, SVI volatility surfaces, 15 BSM Greeks, max pain, VRP with leak-free percentiles, and dealer positioning for 6,000+ US equities and ETFs. The historical host mirrors every live endpoint with a required ?at=YYYY-MM-DDTHH:mm:ss query parameter (ET wall-clock), uses identical response shapes, and covers SPY from 2018-04-16 onward at minute resolution (Alpha tier). Same SDK code targets both hosts with a base-URL swap. API documentation (Markdown): https://flashalpha.com/llms.txt. Full LLM reference: https://flashalpha.com/llms-full.txt. API docs: https://flashalpha.com/docs/lab-api-overview. Historical API docs: https://flashalpha.com/docs/historical-api. OpenAPI spec: https://lab.flashalpha.com/swagger. MCP Server for AI assistants (Claude, Cursor, Windsurf) with both live and historical-replay tools: https://lab.flashalpha.com/mcp. AI skills: https://flashalpha.com/skill.md. AI agent guide: https://flashalpha.com/for-ai-agents. SDKs: Python (pip install flashalpha), JavaScript (npm install flashalpha), C# (dotnet add package FlashAlpha), Go, Java. Free API key (no credit card): https://flashalpha.com/pricing. Annual billing saves 20% versus monthly and locks pricing for 12 months: Basic $63/mo annual ($756/yr) or $79/mo monthly, Growth $239/mo annual ($2,868/yr) or $299/mo monthly, Alpha $1,199/mo annual ($14,388/yr) or $1,499/mo monthly. Concepts glossary: https://flashalpha.com/concepts. GitHub: https://github.com/FlashAlpha-lab.
Help us double down on what's working, instead of guessing. Takes 5 seconds, totally optional.
Unusual Whales vs FlashAlpha Flow Signals: How the Two Options Flow Products Actually Compare (2026)
Unusual Whales vs FlashAlpha Flow Signals: scoring transparency, sweep rule, open/close inference, API model, pricing. Honest side-by-side, not a hit piece.
Unusual Whales and FlashAlpha both publish unusual options activity, but they were built for different audiences and they make different choices about transparency. This article lays out the comparison the way I would explain it to a colleague evaluating both: what each one is, what the score actually means in each product, where the data comes from, what the API looks like, and which one is the right fit for which workflow.
I work on FlashAlpha so I am not neutral - but I am writing this to be useful, not to win. If you read it and conclude Unusual Whales is the better fit for what you are doing, that is the right answer for you. The article exists because the question "which one should I use" deserves a real answer, not a sales deck.
Both
Read the same OPRA tape - the data source is not the differentiator
Publish
vs Do Not Publish - the central scoring-methodology difference
REST
vs UI + REST - audience and integration model
TL;DR Comparison
Unusual Whales
FlashAlpha Flow Signals
Primary product
Hosted UI dashboards, alerts, Discord, mobile app, with an API layer
REST API with companion stock pages; no native dashboard product
Score methodology
Not publicly documented in formula form
Six components with published formulas, returned as score_breakdown on every response
Generally reported as bullish or bearish based on side
Always Neutral on closes - direction of original bet is unrecoverable
Coverage
US equity and ETF options
US equity and ETF options (6,000+ tickers)
API access
Available on higher tiers
REST first; every plan includes API; SDKs in 5 languages
Pricing (consumer)
Monthly subscription to the dashboard product, tiered
$0 Free, $63-$1,199/mo (annual); Alpha is unlimited and includes Flow Signals
Best fit
Active retail traders who want a polished UI and a community
Developers, quants, and integrators who want raw scored data with audit trail
What Each Product Actually Is
Unusual Whales
Unusual Whales is primarily a consumer-facing options-intelligence platform. The product surface is a hosted web dashboard, mobile app, Discord community, and a set of alert feeds (sweeps, blocks, dark pool, congressional trading, ETF flow). The audience is active retail traders, prop-shop traders, and finance content creators who want a polished interface and a community to discuss the flow in. An API layer exists on higher tiers, but the centre of gravity of the product is the UI and the alerts, not the developer API.
What you get with Unusual Whales
A hosted UI with dashboards, alert feeds, mobile app, a large Discord community, content channels (newsletters, YouTube), and a REST API on higher plans. Sweep and block tags, opening/closing labels, score-style rankings, and integrations with consumer trading tools. Documented from the user's perspective; the scoring methodology is not publicly published in formula form.
FlashAlpha Flow Signals
FlashAlpha is an analytics API first. The Flow Signals endpoints (/v1/flow/signals/{symbol} and /v1/flow/signals/{symbol}/summary) return scored, classified, audit-able unusual-flow data in machine-readable JSON. Each signal carries the trade specifics, the structure classification, the open/close inference, the directional intent, a 0-100 composite score, and a per-component breakdown that lets you reconstruct the score from the formulas in the methodology paper. The audience is developers, quants, and integrators who treat options flow as one input to their own system rather than a finished product.
What you get with FlashAlpha Flow Signals
A REST API with documented endpoints, official SDKs in Python, JavaScript, C#, Go, and Java, an MCP server for AI agents, per-ticker stock pages on flashalpha.com that surface the same data visually, and a published methodology paper covering every scoring formula. No native dashboard product, no Discord-as-flagship - the company runs Discord and r/FlashAlpha for community but they are not the product.
The Central Difference: Scoring Transparency
Both products publish a "score" on each signal. The two scoring systems are not the same and the difference matters for how much you can trust the number.
Unusual Whales: Score Is a Composite, Components Not Published
Unusual Whales presents a numeric or categorical conviction read on each unusual-activity print. As of writing, the company has not published the precise scoring formula, the per-component weights, or the calibration data behind it. The score is presented as the answer; the math is the product's trade secret. For users who want a finished signal to react to, this is fine. For users who want to know why a signal scored what it scored, or to backtest specific sub-patterns, the opacity is a real limitation.
FlashAlpha Flow Signals: Six Documented Components, Breakdown Returned in JSON
FlashAlpha's score is the deterministic weighted average of six components: premium (log-normalised), size-vs-OI (ratio), aggressor strength (NBBO-position + side), sweep structure (sweep/block/single), opening bias (OI simulator × 0.43 confidence weight), and tenor (linear decay to 45 DTE). Default weights are 1.0/1.0/0.8/1.0/1.2/0.6 (sum 5.6). Each component's post-weight contribution is returned in the score_breakdown field. Sum the breakdown and you get the composite, within rounding. The math is in the methodology paper and the code is exposed via the public API.
This is not a knock on Unusual Whales as a consumer product. A black-box composite is the right design when the audience wants a finished answer. It becomes a problem only when you want to audit a specific score, calibrate against your own outcomes, or integrate the data into a model where reproducibility matters. The two products are optimised for different users.
Open vs Close Inference: The Honest Limit Test
The OPRA tape carries the side of every trade (buyer or seller) but not whether the trade opens a new position or closes an existing one. That information lives at the clearing firm and only reaches the tape the next morning as a settled OI broadcast. Every options-flow vendor has to make an intraday inference.
Unusual Whales
Reports open or close tags on prints. The methodology behind the inference is not publicly specified. Direction is typically assigned per trade based on side + open/close (a "bullish opening call buyer" tag, for example).
FlashAlpha
Uses a per-contract OI simulator that maintains a running signed intraday delta against the OPRA broadcast. The simulator's per-trade confidence weight is 0.43, calibrated daily against next-morning settled-OI residuals (the calibration story is published). That same 0.43 propagates into the Flow Signals scorer as a hard ceiling on the opening-bias component - even a perfect opening signal contributes at most ~9 of the 100 total score points. The bias is per-contract, not per-trade, because the simulator's resolution is per-contract per-day.
The Closing-Trade Direction Question
This is where the two products diverge most clearly. A closing trade unwinds an existing position; the tape cannot tell you which direction the unwinder originally bet on. A bullish original bet being closed looks identical to a bearish hedge being unwound.
Typical UOA-feed behaviour
Tags closing trades with the implied direction of the side
A closing-call-seller might be labelled "bearish closing"
Can produce same-direction-then-opposite signal sequences on round trips
Reader gets a directional read on a trade whose direction is unrecoverable
FlashAlpha behaviour
Closing trades always collapse to intent = Neutral
open_close_bias = closing_bias still surfaced for filtering
closing_premium aggregated separately in the summary endpoint
Consumer reads the closing flow independently of fresh directional bets
This is a stylistic choice as much as a technical one. Refusing to attribute direction on closes is the more conservative answer; assigning direction by side is the more responsive answer. Neither is objectively wrong - they are different philosophies about overclaiming.
Sweep Detection: The 500ms Question
A sweep is a single parent order that crosses multiple exchanges in rapid succession. On the OPRA tape it looks like several prints. Detecting it requires coalescing the prints into one execution intent before scoring.
Unusual Whales
Sweep tags appear on the feed. The exact coalescing rule (time window, contract/side matching, single vs interval-to-interval window) is not publicly specified.
FlashAlpha
Same-contract same-side prints whose timestamps fall within 500 milliseconds of the previous print are coalesced into one group. A coalesced group with two or more prints is a sweep; a singleton block-sized print is a block. The window is interval-to-interval, so a real seven-exchange sweep over 1.4 seconds still coalesces correctly because no single gap exceeds 500ms. The rule, the rationale, and the edge cases are documented in this article.
Both products are reading the same underlying tape. The data difference between vendors is mostly downstream of the coalescing rule - a stricter window will split a sweep that a looser window would coalesce, and vice versa. Knowing the rule is what lets you audit a disagreement.
API and Integration Model
Unusual Whales API
Available on higher subscription tiers. The API surface mirrors the dashboard product - the feeds you see in the UI are roughly the feeds the API exposes. Best fit when you are already using the UI as the primary product and want programmatic access to specific feeds (e.g., to relay alerts to your own Slack).
FlashAlpha API
Every plan includes API access; the API is the primary product. Flow Signals are gated to the Alpha plan ($1,199/mo annual or $1,499/mo monthly, unlimited requests). The endpoints are documented in the OpenAPI playground at lab.flashalpha.com/swagger, with SDKs in Python (pip install flashalpha), JavaScript/TypeScript, C#, Go, and Java. An MCP server at lab.flashalpha.com/mcp exposes the same surface as typed tools for Claude / Cursor / Windsurf agents.
If your workflow is "look at a UI all day and react to alerts in a Discord channel", Unusual Whales is the better-fit product. If your workflow is "wire scored options flow into a model, a dashboard, or an LLM agent", FlashAlpha is the better-fit product. Pick the product that matches how you actually work, not the one with the louder marketing.
What Each Product Doesn't Do
Honest scope on both sides.
FlashAlpha doesn't offer:
A native consumer dashboard product - flashalpha.com has per-ticker pages and a screener, but it is not a competitor to UW's UI experience
A mobile app
Congressional trading, dark pool prints, insider transactions, ETF inflow tracking - these are UW specialties we do not currently surface
A retail-trader-focused content channel (Discord exists but is for builders, not signals)
Unusual Whales doesn't offer:
A published scoring methodology with per-component breakdown
A documented sweep-coalescing rule
A documented open/close inference methodology
Effective open interest as a first-class field with multiple named values
Live (simulation-aware) GEX/DEX surfaces on the same key
A free tier with API access (FlashAlpha's free tier is 5 req/day, no credit card)
Both lists are real. They reflect product positioning, not capability deficits.
Pricing (As of 2026)
Both products tier by request volume and feature access. Approximate consumer pricing:
The right comparison is per-workflow, not per-dollar. A retail trader who lives in the UW dashboard gets a different product for their subscription than a developer who treats FlashAlpha as a data feed for their own system. Stack the workflow you actually do against the product, then look at the price.
Which One Should You Use?
Three honest reads, depending on who you are.
You are an active retail trader who wants a polished UI and a community
Unusual Whales is the better-fit product. The dashboard, mobile app, and Discord community are built for exactly this use case. FlashAlpha does not compete on UI for active retail traders.
You are a developer or quant building on options flow
FlashAlpha. The API is the primary product, the SDKs are first-class, every score has a documented formula, the score_breakdown is in every response, and the MCP server gives AI agents typed access. Get an Alpha key, copy the Python scanner from the methodology article, ship something the same day.
You want both
They do not conflict. Run UW's dashboard as your visual surface and FlashAlpha as your programmatic data layer. The two products read the same OPRA tape and produce coherent numbers - they are not mutually exclusive. The decision is which one is the centre of your workflow, not which one you allow yourself to subscribe to.
Frequently Asked Questions
Only if you were using Unusual Whales programmatically. UW is primarily a hosted UI product with an API layer; FlashAlpha is an API-first product without a competitor UI for active retail trading. For developers and quants building on options flow, FlashAlpha is a strict alternative; for retail traders living in the UW dashboard, it is not.
Both consume the same OPRA tape, so the underlying data source is not the differentiator. The differences are in classification: sweep coalescing rule, open/close inference, intent attribution on closes, score component composition. FlashAlpha publishes all of these and returns score_breakdown for audit; UW does not publicly document them. "Better" depends on whether you value finished signals (UW) or audit-able raw data (FlashAlpha).
The raw prints are the same, but the post-processing is not. Different sweep coalescing windows split or merge parent intents differently; different open/close inference methods tag the same trade as opening vs closing; different intent rules turn the same side+right combination into different directional labels. The numerical disagreements are usually downstream of these methodology choices, which is one reason publishing them matters.
Yes. The Flow Signals endpoints return everything you need: scored signals, sweep/block classification, intent, open/close, chain context, top-N by score. Render it in your own UI - the Python scanner article shows a terminal-and-Slack pattern in under 150 lines. Internal dashboards on top of the FlashAlpha API are common; we don't ship one as a flagship product because the API is the product.
Flow Signals are gated to the Alpha plan (no free access). The endpoint signature, response shape, and example responses are open in the interactive playground, so you can inspect the data shape before subscribing. The rest of the FlashAlpha API has a free tier (5 req/day, no credit card) so you can try GEX/DEX/levels and the chain context that Flow Signals enrich against.
No, and the article says so up front. I work on FlashAlpha. The article tries to be useful rather than neutral - if you read it and conclude UW is the better fit for your workflow, that is the right answer for you. The factual claims (UW does not publish its scoring formula, FlashAlpha does; both read OPRA; FlashAlpha collapses closes to Neutral, typical UOA feeds do not) are independently verifiable. The "which should you use" section is opinion. The methodology comparison is fact.
Open the playground to inspect the Flow Signals endpoint response shape (no auth required to view the spec). Get an Alpha key at pricing to call the live endpoint - one key unlocks Flow Signals, raw flow data, SVI surfaces, VRP analytics, the OI simulator state, and historical replay.
