The Oracle · Polymarket

Will Amazon.com, Inc. (AMZN) hit (HIGH) $280 in July?

Predicted · Resolved

Pythia’s forecast Resolved: NO correct
12.0% Our forecast
19.7% Market at prediction
-7.7pp Edge
70% Confidence

Analysis

[REDIRECT -> sibling 2677512 @ 72%, restated P=96%] The ensemble is coherent and well-researched on the $280 question: ~12% fair value versus 19.7% market gives a real but modest NO edge in a coarse threshold ladder. However, the sibling ladder reveals a much larger, verifiable mispricing: the $256 HIGH market trades at 72% even though AMZN printed $258.08 during the July 16 regular session — a threshold that appears already achieved under the market's Pyth RTH 1-minute-candle rules. Since all siblings price the same underlying quantity (AMZN's July price path) that the ensemble already researched, I redirect the trade to sibling 2677512 with P(YES)≈0.96 (small haircut for Pyth-vs-exchange data risk plus a forward-path fallback of ~57% if the print somehow doesn't qualify). This ~24-point edge dominates the ~8-point NO edge on the $280 market. For the market under review I keep the ensemble-consistent 12%.

Key Evidence

Verified via CNBC, CNN, Robinhood, and Yahoo/Investing.com daily history: AMZN traded to $258.08 on July 16, 2026 (session open $255.12, low $248.00) — a regular-session high per standard OHLC conventions. This means the $256 HIGH sibling threshold has already been satisfied, yet that market prices only 72%. For the $280 market under review, all agents agree it requires +12% in ~10 sessions with only one post-earnings session in-window and options implying ~8% earnings move; fair value ~12% vs 19.7% market.

Risks

The trade lost because the $258.08 July 16 'high' was actually a pre-market or consolidated-tape print that Pyth's regular-hours 1-minute candles never captured, AND AMZN then slid post-earnings without ever touching $256 in RTH before July 31 — leaving the $256 threshold unmet despite quote pages showing it as the day range.


Provenance

This analysis is timestamped via OpenTimestamps — anchored in Bitcoin block 959123 — proving it existed before the outcome was known.

SHA-256: 0079af1a8e60310d60225a4c76fc8c2c9aa8a99693c918e9d0102a53686852c7

Download content.md · Download .ots proof

Verification needs both files: confirm the text’s hash with sha256sum content.md, then check the proof against it — drag both into opentimestamps.org or run ots verify content.md.ots locally.

This page is for informational and research purposes only. Nothing here constitutes financial advice.