Skip to content

Intelligence engines

Expected Points: what the usage should have produced

What a player's real usage should have produced: expected points from the carries, targets, air yards, and field position he actually saw, independent of whether the ball bounced his way.

How we read it

xFP: expected, not actual

ffverse's ff_opportunity models the fantasy points a usage profile should yield. Expected points persist far better than actual points, which swing on touchdown luck.

Buy-low: expected outruns actual

When the expected percentile sits well above the actual percentile, the usage says the production is coming. Buy-low before it corrects.

Sell-high: actual outruns expected

When actual outruns expected, the player is running hot on conversion luck. Sell-high before it regresses. In-line means the points are earned by the opportunity.

for PRO members only

Expected Points: what the usage should have produced

Expected Points: what the usage should have produced is a Pro-tier analytics engine. This is the same data served by the premium /api/intelligence/expected-points endpoint, gated for Pro and Elite members.

founding rate · locked for life · 3-day refund window

Expected points data from ffverse/ffopportunity (CC-BY-SA-4.0) How we source data

More engines & APIs5 engines without a standalone boardExtra feeds and player boards. Expand to browse them.

Roster Advice

Turns a posted roster into real add / drop / hold decisions (pairs with league sync).

Graded Pool

Combines the player grade, expected points, team environment, and passing signal into one ranked pool that feeds every fantasy tool.

QB Consensus

Two public QB ratings side by side. When they disagree, we show it instead of averaging it away.

Rushing Efficiency

Yards over expected per carry, next to volume and stacked-box context: bell-cow, buy-low, or volume-dependent.

Receiving Opportunity

Air yards and target share combined into one opportunity score, with a clear buy / sell read.