Roster Advice
Model → real add/drop/read decisions for a posted roster (composes with Sleeper sync).
Intelligence engines
Expected Fantasy Points: the opportunity backbone
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.
Rights-gated
This engine is intentionally unavailable.
Expected points (ffverse/ffopportunity) is licensed CC-BY-SA-4.0 (share-alike), which is not cleared for customer display while the share-alike question is open. This surface stays intentionally empty rather than showing data we do not hold display rights for.
Expected points data from ffverse/ffopportunity (CC-BY-SA-4.0) How we source data
More engines & APIs5 engines without a standalone boardPOST-only, founder-gated, or rendered on the player boards under /players. Expand to browse them.
Graded Pool
Composes the model + xFP + team environment (real schemeFit from neutral-script offensive EPA) + QB-forward passing signal into a real graded pool that drives every fantasy tool when the founder enables it.
QB Consensus
ESPN QBR (results) vs Next Gen CPOE (accuracy), triangulated. Disagreement surfaced, not averaged.
Rushing Efficiency
RYOE/att vs volume with stacked-box context: bell-cow / buy-low / volume-dependent.
Receiving Opportunity (WOPR)
Air-yards & target share → WOPR, with opportunity-vs-production buy/sell.