G2

Coco N.

Software Engineer

Small-Business (50 or fewer emp.)

7/13/2026

"Deep, Differentiated Dealer-Positioning Data and a Broad Options Analytics API"

5/5

What do you like best about FlashAlpha?

The depth and honesty of the dealer-positioning data is what really sets it apart. Most GEX providers give you a single net-gamma number based on open-interest assumptions; FlashAlpha exposes the whole stack: settled-OI and flow-simulated effective-OI, per-strike GEX/DEX/VEX/CHEX, and the ?polarity=flow overlay that signs each strike by the measured dealer position from the classified tape rather than the calls-positive/puts-negative convention. That last piece is genuinely differentiated. Being able to answer “are dealers actually long or short gamma today?” versus “what do the option types imply?” has changed how we read the tape.

The other standout is how much breadth is wired into one API: GEX ladders, 0DTE flow/pin-risk/hedge-flow, VRP with gex-conditioning, an SVI surface plus variance-swap fair values, earnings IV-crush, dispersion, and a historical replay host that lets us backtest all of it point-in-time. We built an entire options desk on it—ladders, a multi-lens trade-assessment engine, 0DTE signals, and a paper loop—without needing a second exposure vendor.

On the practical, day-to-day side, the endpoints degrade gracefully (uncovered symbols and off-hours calls return clean empties instead of erroring), coverage is upfront about its own limits, and support has been responsive when we’ve reported data-quality issues. The data_quality scores, along with the FA-native narrative/synthesis reads, also mean we’re often surfacing FlashAlpha’s own analysis rather than having to reinvent it. Review collected by and hosted on G2.com.

What do you dislike about FlashAlpha?

Documentation lags behind the product. The API’s capabilities are excellent, but the docs trail the actual endpoints by weeks. Several features we rely on (?polarity=flow, the calibrated 0DTE pin/range probabilities, historical flow replay) ship and work before they show up in api.md, and some are only documented in blog articles rather than in the main reference. For example, historical /v1/flow/*?at= routes serve full data but aren’t listed in the historical-API docs at all, which still imply flow is live-only. More than once we’ve had to confirm a capability by live-probing instead of reading, so the trust order ends up being live probes > changelog > docs pages, which really shouldn’t be the case.

There are also a few silent-failure edge cases. The worst is ?polarity=flow on a day with no stored data: instead of 404ing like structural mode, it returns 200 with every strike zeroed. That’s indistinguishable from a genuinely flat-tape reading, so it can silently poison a backtest with no obvious error to catch. There are smaller cousins of this too (0DTE expected_move returning degenerate 0 rows off-hours, /exposure/sheet silently returning full-chain aggregates when ?expiry= is passed instead of ?expiration=). Failing loudly and honestly, rather than returning plausible-but-wrong values, would save a lot of debugging time.

Field conventions are inconsistent across endpoints. The same concept shows up under different names and units depending on the route: /flow uses live_net_gex/live_gamma_flip while /exposure uses net_gex/gamma_flip; IVs are percent-points on /vrp but decimals on /strategies/tail-pricing; some endpoints take ?expiry= while others take ?expiration=, and passing the wrong one can fail silently. None of these are dealbreakers, but they’re constant papercuts that force defensive .get() fallbacks everywhere.

Historical collection also has occasional single-day gaps. It’s mostly backfilled well, but the odd trading day goes missing and needs a support nudge—fine for research, less ideal if you’re depending on an unbroken series.

To be clear, none of this outweighs the data quality. Support has been responsive when we’ve reported these issues, and most feel like fixable-in-a-sprint documentation and error-handling gaps rather than anything fundamental. Tightening docs-to-release parity and making failures loud instead of silent would be the single biggest quality-of-life improvement. Review collected by and hosted on G2.com.

What problems is FlashAlpha solving and how is that benefiting you?

The core problem it solves is visibility into dealer positioning—the thing that actually moves intraday price around option strikes, but that retail traders normally can’t see. It shows where price is likely to pin, where dealer hedging amplifies versus suppresses volatility, and where the real walls are versus where open-interest convention implies they are. FlashAlpha turns all of that into a clean API, instead of something you’d need a Bloomberg terminal and a quant to approximate. The polarity=flow signing (measured dealer position, not OI assumptions) in particular answers a question we simply couldn’t answer before: “Are dealers genuinely long or short gamma right now?”

The second problem is fragmentation. Building any serious options tooling normally means stitching together a GEX provider, a separate vol-surface/SVI source, an earnings/IV-crush feed, a VRP calculator, a flow tape, and a historical vendor for backtesting. FlashAlpha consolidates all of that into one consistent API, with a matching historical-replay host. We built an entire options desk—live GEX ladders, a multi-lens trade-assessment engine, 0DTE signal detection, and a paper-trading loop—on FlashAlpha alone, without a second exposure vendor.

The concrete benefit is that decisions are grounded in dealer-flow reality instead of guesswork. Our trade selection, risk flags, and 0DTE reads all key off measured positioning, and because the historical API replays the same data point-in-time, we can actually backtest whether a signal has edge before trusting it. That has stopped us from shipping several plausible-but-worthless signals. Overall, it compressed what would have been a multi-vendor, multi-quarter build into a single, well-covered data source, and moved our workflow from “eyeball the chart” to “read what dealers are positioned to do.” Review collected by and hosted on G2.com.