Five names came back above a 60% consensus gap this week, and sorting them by size hides the more useful distinction. Three of them got there because the share price fell away from targets that had not yet been revised. Two got there because the operating outlook improved and the targets moved up while the price lagged. Same screen, same ranking, opposite mechanisms, and only one of them tells you anything about analyst conviction.
The gaps here come from FMP's Price Target Summary Bulk API. This article works through the five and then sets out the workflow the endpoint anchors.
Key Takeaways
- Three of the five gaps opened because price fell, not because targets rose, which makes them a measure of revision lag rather than analyst conviction.
- AppLovin tops the screen at 81.4% after a revenue miss took roughly a fifth off the shares, with a target average built largely before that print.
- ESAB and Kratos are the exceptions: both raised their outlooks, so their gaps reflect targets moving up ahead of price rather than the reverse.
- Coverage depth separates the reliable readings from the fragile ones, and it ranges from 19 contributing targets on Oracle to 3 on ESAB.
Five Names Where Price and Consensus Parted
AppLovin Corporation (NASDAQ: APP)
Current Price: $315.44 • Consensus Target: $572.29 • Upside Potential: 81.4%
AppLovin carries the widest gap in the screen, and it opened almost entirely in one session. Second-quarter revenue came in below expectations, the shares fell roughly 20% on the print, and several desks moved their ratings down afterwards. The average target here draws on 14 contributing estimates over the last quarter, most of them set when the shares traded materially higher, which means the gap is measuring the interval between a price adjustment and the revision cycle that follows it rather than a considered view that the stock is worth 80% more.
That timing effect is the thing to isolate. The quarter was not uniformly weak: profitability held up, buyback activity continued, and a regulatory overhang was clarified during the period. What moved the shares was the top line and the guidance that accompanied it, in a name where the multiple had been underwritten by the assumption that advertising revenue would keep compounding at an elevated rate. When a growth premium is the whole valuation, a revenue miss is not a small adjustment.
Reading this correctly means working from FMP's Historical Stock Grades API, which shows the sequence of rating changes rather than the current snapshot. A cluster of downgrades arriving after a price move, with targets not yet reset, is a specific and temporary configuration. Tracking where the target average settles over the following weeks is what distinguishes a genuine consensus gap from an artefact of the calendar.
Wingstop Inc. (NASDAQ: WING)
Current Price: $126.12 • Consensus Target: $210.08 • Upside Potential: 66.6%
Wingstop's gap rests on 12 contributing targets and on a genuine split within the business. Domestic same-store sales fell 7.5% in the second quarter and the company cut its full-year comparable sales outlook to a decline of 4% to 6%. In the same release it reiterated global unit growth of 15% to 16%, opened 102 restaurants in the quarter, and reported loyalty sign-ups running well ahead of the prior year.
Those two facts are not contradictory, and the tension between them is the whole analytical question. A franchised restaurant model earns from system-wide sales, so unit expansion and comparable sales pull in opposite directions on the same revenue line. Rapid unit growth against negative comparable sales can indicate either that new locations are cannibalising existing ones or that the brand is expanding faster than existing-store traffic can keep pace with, and the two have very different implications for average unit volumes over time.
The consensus position on that trade-off shows up in FMP's Financial Estimates API, where forward revenue and earnings estimates embed a view on how those two variables reconcile. If forward estimates have come down alongside the guidance cut while targets have not, the gap is stale in the same way AppLovin's is. If estimates have held on the strength of unit growth, the desks are expressing a genuine view that the comparable sales pressure is transitional.
ESAB Corporation (NYSE: ESAB)
Current Price: $84.81 • Consensus Target: $139.33 • Upside Potential: 64.3%
ESAB is one of two names here where the gap did not open through a price decline. The company reported record second-quarter sales, beat expectations, and raised its 2026 outlook, with equipment strength and the integration of its Eddyfi acquisition featuring in the results. The gap therefore reflects targets that moved up on an improving outlook while the share price has been slower to follow.
The caveat is coverage. This average rests on only 3 contributing targets over the last quarter, the thinnest in the screen by a considerable margin, which makes the figure far more sensitive to any single desk's assumptions than the Oracle or AppLovin numbers are. A wide gap backed by three estimates and a wide gap backed by nineteen are not the same observation, and the screen presents them identically. The operating story is the more solid part of this entry; the consensus number attached to it is the fragile part.
Given the acquisition, the follow-up belongs in FMP's Balance Sheet Statement API: a raised outlook arriving alongside an integration needs to be read against the leverage and working capital position funding it. Welding and fabrication equipment is a cyclical business tied to industrial capital spending, and the durability of the outlook depends on whether the raise reflects underlying demand or the arithmetic of consolidating an acquired revenue base.
Oracle Corporation (NYSE: ORCL)
Current Price: $150.32 • Consensus Target: $244.74 • Upside Potential: 62.8%
Oracle produces the best-supported gap in the screen, with 19 contributing targets, and it is also the clearest case of price and consensus disagreeing about the same known facts. Cloud infrastructure revenue has been growing at a rate few businesses of this size achieve, with a recent quarter posting growth above 90%, while the shares have spent the year well below their highs and near the lower end of their fifty-two-week range.
The disagreement is about the cost of that growth rather than the growth itself. Capital expenditure forecasts for the year have been revised toward levels that would have been unimaginable for this company a few years ago, and building infrastructure capacity at that scale consumes cash upfront against revenue that arrives over the life of the contracts. The market is applying a discount for the capital intensity and the margin profile of the infrastructure business relative to the legacy software base. The desks maintaining higher targets are underwriting the eventual return on that spending. Both positions are consistent with the same reported numbers.
Adjudicating it takes FMP's Cash Flow Statement API, because operating cash flow against capital expenditure is the single series that shows whether the build is self-funding or drawing on the balance sheet. Free cash flow trajectory, tracked quarter by quarter through a capital cycle of this size, is what will resolve the disagreement, and it will do so before any change in the revenue growth rate becomes visible.
Kratos Defense & Security Solutions (NASDAQ: KTOS)
Current Price: $64.58 • Consensus Target: $104.00 • Upside Potential: 61.0%
Kratos closes the list with 10 contributing targets and, like ESAB, a gap that opened from the target side rather than the price side. Second-quarter results were driven by strength in missile systems and engine sales, following an earlier raise to full-year revenue guidance, and the company sits in a segment of the defence market where procurement priorities have shifted toward unmanned systems and lower-cost munitions.
The interesting feature is where the growth is actually coming from. The commentary around this name has been dominated by drones, while the reported outperformance leaned on missile and engine work. That is not a contradiction, but it does mean the narrative driving sentiment and the business driving results are currently different things, which is worth holding separately when interpreting a target set built partly on the former.
Segment-level contribution, available through FMP's Revenue Product Segmentation API, shows which product lines are carrying growth rather than which are carrying attention. In a defence business where programme timing determines revenue recognition, tracking the mix across several quarters is what establishes whether the raised outlook rests on a broadening base or on a small number of programmes moving through their delivery schedule.
Two Very Different Kinds of Gap
The screen ranks these five between 61% and 81%, a narrow band that makes them look like variations on one finding. They are not. AppLovin, Wingstop and Oracle arrived here because their share prices fell away from a target set that had been established earlier. ESAB and Kratos arrived because both raised guidance and the targets moved up faster than the price did. A ranking sorted on gap size cannot distinguish those two, and they carry close to opposite information about how much analyst conviction sits behind the number.
Coverage depth compounds the problem. Oracle's 62.8% gap draws on 19 contributing targets and represents a real and specific disagreement about capital intensity in a business whose growth rate nobody disputes. ESAB's 64.3% gap draws on 3, which makes it a reading with a wide confidence interval around it rather than a consensus in any meaningful sense. The two figures sit one percentage point apart in the ranking and are not comparable observations.
That is why the gap alone is the least useful output of this screen. Within the FMP data environment, the Price Target Consensus API adds the dispersion around the average, and dispersion is what separates broad agreement from a mean pulled by one outlying estimate. Setting that against the Historical Stock Grades API establishes the direction of travel, since a wide gap where recent actions have been downgrades is a gap in the process of closing from the target end, not the price end.
The layer that settles it is the estimate base itself. The Financial Estimates API shows whether forward revenue and earnings forecasts have moved with the targets or been left behind by them, and that single comparison sorts this week's five cleanly. Where estimates have fallen and targets have not, as looks likely for the names that de-rated on guidance, the gap is measuring revision lag. Where estimates have risen with the targets, as at ESAB and Kratos, the gap is measuring an actual difference of view between the desks and the market. Adding the Ratings Snapshot API confirms whether the current distribution of ratings is consistent with the target level or has already begun to diverge from it. A gap that survives all three tests is worth the research time. A gap that does not has told you something about the calendar.
Creating a Structured Target-Gap Workflow
A price-target spread only becomes useful when the calculation can be reproduced reliably. That means fixing the data inputs, pulling them in a consistent sequence, and applying the same formula every time the screen runs. Once those elements are standardized, the exercise stops being a one-off comparison and turns into a process that can be refreshed on a schedule.
The only requirement before running the workflow is a valid API key.
Step 1: Pull Analyst Price Targets
The process starts by establishing where consensus currently sits. This is done by querying the Price Target Summary Bulk API, which returns average price targets along with analyst participation counts across the ticker set in a single call. That combination matters: the average target provides the reference level, while coverage depth helps contextualize how representative that number is. Together, they form the baseline against which market prices will be compared.
Endpoint:
|
https://financialmodelingprep.com/stable/price-target-summary-bulk?apikey=YOUR_API_KEY |
Sample Response:
|
[ { "symbol": "AAPL", "lastQuarterCount": "12", "lastQuarterAvgPriceTarget": "228.15", "lastYearAvgPriceTarget": "205.34" } ] |
Step 2: Pull Latest Market Prices
Once targets are in place, the next input is the current trading price. This comes from the Company Profile Data API, which includes the most recent quote used for comparison. At this stage, the goal isn't granularity or intraday precision — it's simply to anchor each name to the same market reference point so gaps are calculated consistently.
|
https://financialmodelingprep.com/stable/profile/AAPL?apikey=YOUR_API_KEY |
Step 3: Derive the Target Gap
Once both values are available, the gap itself is straightforward to compute. Express it as a percentage to normalize results across different price levels:
Upside % = (Price Target - Current Price) / Current Price × 100
Using percentages allows large-cap and lower-priced names to sit in the same ranking without distortion.
Step 4: Apply a Threshold Filter
The final layer is judgment. Most workflows introduce a minimum threshold — often around 20% — to filter out routine variance and focus attention on gaps that are large enough to matter. At this stage, analyst coverage becomes part of the interpretation: a wide gap backed by broad, recent coverage carries a different weight than one driven by a small or outdated estimate set.
Structured this way, the process moves beyond a simple valuation screen. It becomes a repeatable diagnostic tool — one that highlights where price and consensus are drifting apart and does so in a way that can be refreshed, audited, and scaled across time and coverage universes.
From Individual Screen to Institutional Research Process
Most quantitative workflows begin quietly — a model or screen built by a single analyst to answer a recurring question with greater consistency. The first version usually lives in a spreadsheet or a small script: efficient, practical, and tailored to the needs of one desk. The turning point arrives when the signal proves useful enough that colleagues begin asking for it. Replication follows, and with it comes an unintended side effect: slight variations in endpoints, refresh schedules, or calculation logic start producing subtly different results.
At that stage, the analyst who created the workflow often becomes an informal architect of standardization. The challenge shifts from running the screen to defining the method behind it. Institutional value emerges when the process is formalized: the data sources are fixed, the sequence of API pulls is documented, formulas are locked, and thresholds are explicitly defined. Once those elements are stabilized, the workflow stops being a personal tool and begins to function as a shared research input.
Moving the process into a centralized dashboard with scheduled updates is usually the next step in that evolution. Instead of circulating spreadsheets or ad-hoc scripts, teams interact with the same data pipeline and the same calculation framework. This reduces workflow fragmentation across research groups and allows portfolio managers, analysts, and risk teams to reference the same signal simultaneously. When everyone is drawing from the same dataset and methodology, discussions shift away from reconciling numbers and toward interpreting what the signal actually means.
Standardization also strengthens governance and transparency. A centralized workflow creates a visible audit trail: where the data originated, when it refreshed, and how each metric was derived. That lineage matters in institutional environments where reproducibility is essential. When colleagues run the same query and obtain the same result, the signal becomes dependable infrastructure rather than a one-off analytical shortcut.
Scaling that kind of workflow across a team requires stable access to the underlying datasets and consistent distribution across users. Infrastructure becomes less about adding features and more about removing friction from the research process. Platforms designed for institutional usage — such as FMP's Enterprise plan — provide the access controls, refresh stability, and shared environment needed when a desk-level workflow transitions into a broader research tool.
When that transition happens successfully, the model itself changes role. The target-gap screen is no longer simply a clever comparison between price and analyst targets. It becomes part of the firm's analytical framework — a standardized diagnostic that multiple teams can rely on to identify where market pricing and consensus expectations are beginning to drift apart.
Gaps Close From Both Ends
A consensus gap has two ways to resolve, and the screen is silent on which one is in progress. That is the argument for treating coverage depth and the direction of recent estimate changes as part of the reading rather than as footnotes to it. Run with those layers attached, FMP's Price Target Summary Bulk API stops producing a list of apparent bargains and starts producing a map of where the market and the desks have not yet finished arguing.
If you enjoyed this analysis, you'll also want to read: Weekly Signals Desk | Concentrated Analyst Revisions via the FMP API (Aug 3-7)
Disclosure: Signals Desk content is provided for informational and analytical purposes only and does not constitute investment advice or trade recommendations. The analysis reflects interpretation of market data and publicly disclosed or third-party information, including data accessed via Financial Modeling Prep APIs, at the time of publication. Signals discussed are probabilistic, can be wrong, and may change as market conditions and consensus data evolve. This content should be considered alongside broader research, individual objectives, and risk assessment.
