forecasting
agent
← back to scans

Will Waymo operate in 12-15 cities on December 31 2026?

polymarketCompanies·2026-09-16·view on polymarket ↗
33%
Agent
28%
Market Price
+4.9%
Edge
60%
Confidence
39,538
Volume
1.7c
Spread
106
Days to resolution
7
Markets in event
final rationale
Waymo already counts 15 public metros, so Yes requires zero additional separately-counted launches over the remaining ~3.5 months; falling below 12 is effectively impossible, so this is a single-sided bet on the pipeline stalling. Detroit (stated 2026 target), Sacramento (CPUC-approved, likely counted as a distinct metro given its distance from the Bay Area), and London (testing with 2026 ambitions) each offer a plausible path to 16, and Waymo's recent cadence of batch launches makes at least one more before year-end more likely than not. Countervailing factors are real: Michigan approval is pending, Sacramento has no firm date, DC is legislatively blocked, and Waymo has repeatedly slipped announced timelines by months. Weighing the thin Polymarket anchor (~28%) against the brief's per-city model (~40%) and the documented blockers, I land near the forecasters' consensus at 33% Yes.
price vs. prediction
market price agent forecast at t+0
32 follow-ups
re-scan context
This market has been scanned before. Previous predictions:
datepredictedmarket priceconfidence
2026-09-01 45% 28% 52%
2026-08-24 38% 44% 46%
1. Planner Fable 5.1 · Fermi decomposition + tool plan
Tools chosen: polymarket_direct polymarket_related kalshi_related claude_news article_search gdelt_news wikipedia earnings_data code_execution
Sub-questions (Fermi decomposition)
  1. How many distinct cities/regions does Waymo currently serve with fully public (non-waitlist, non-invite) ride-hailing via Waymo One or Uber, under this market's counting rules?
  2. Which additional cities has Waymo officially announced for public launch by end of 2026, and how many have a stated 2026 timeline versus vague or 2027 timelines?
  3. What is Waymo's historical lag between announcing a city and opening fully public service (e.g., Austin, Atlanta, Miami, DC), and how often have announced launch dates slipped?
  4. Are there regulatory or legislative blockers (e.g., Washington DC, New York, Boston, Tokyo, London) that could delay specific announced cities past Dec 31 2026?
  5. What are Waymo's vehicle production (Zeekr/Hyundai/Jaguar) and fleet-scaling constraints, and do they limit the number of simultaneous new-city launches in 2026?
  6. How do the sibling Polymarket buckets (<12, 12-15, 16-19, 20+) and any Kalshi Waymo markets price the end-2026 city count distribution?
  7. How will ambiguous cases (e.g., Bay Area vs. San Jose/Silicon Valley, LA County, Phoenix metro, Uber-only cities like Austin/Atlanta, freeway-only expansions) be counted under the resolution rules?
Planner reasoning
This is a Polymarket bucket question on Waymo's public city count at end of 2026. Key drivers are the current count of publicly available cities (counting metro regions as one), the pipeline of announced 2026 launches (Miami, DC, Dallas, Denver, Nashville, Las Vegas, San Diego, Detroit, Houston, San Antonio, Orlando, London, Tokyo, etc.), Waymo's historical announcement-to-public-launch lag, and regulatory/vehicle-supply constraints. Cross-checking sibling bucket markets and Kalshi will anchor the distribution.
2. Research Parallel tool calls
toolstatustimeitemssummary
polymarket_direct OK 0.5s 1 ## This Market's Polymarket Data **Will Waymo operate in 12-15 cities on December 31 2026?** - Current price (probability): 28.05% - 7-day price change: +0.20% - 30-day price change: +4.55% - Total volume: $39,538 (USD notional) - Price range: 0.35% - 56.10% - Data points: 83 days
polymarket_related OK 1.0s 0 Scanned 100 active Polymarket markets, kept 0 matches. keyword 'Waymo': 0 markets | keyword 'robotaxi': 0 markets | keyword 'autonomous': 0 markets
kalshi_related OK 0.8s 0 0 related markets / summaries. keyword 'Waymo': no matches | keyword 'robotaxi': no matches
claude_news OK 42.7s 8 Here are the key findings on Waymo's city footprint and 2026 pipeline (as of September 16, 2026): **Currently public (no waitlist/invite-only restriction removed) — 15 cities:** - Waymo has expanded to 11 cities around the country, with four more on the way as of July 19, 2026 — those "four more"
article_search OK 0.9s 22 Fetched 22 unique articles across 5 queries (lookback=90d). 'Waymo launches public service new city': 10 articles | 'Waymo expansion 2026 cities announced': 10 articles | 'Waymo Uber robotaxi launch': 10 articles | 'Waymo regulatory approval delay robotaxi': 10 articles | 'Waymo fleet Zeekr Hyundai
gdelt_news OK 96.3s 30 GDELT: 30 articles across 3 queries (lookback=60d). 'Waymo launch': 10 hits | 'Waymo expansion': 10 hits | 'Waymo London Tokyo': 10 hits
wikipedia OK 0.2s 1 Fetched 1 Wikipedia entries (0 missing pages).
earnings_data OK 0.2s 1 Fetched FMP data for 1 ticker(s).
code_execution OK 39.2s 0 ## Monte Carlo Simulation Results — Waymo City Count by Dec 31, 2026 **Model setup:** Base current count sampled from {8, 9, 10} (30/40/30% weights, reflecting counting-rule ambiguity), plus 12 independent Bernoulli draws for announced 2026 launch candidates (San Diego 0.85, Las Vegas 0.85, Detroit
3. Evidence Brief Sonnet 5 · 7093 chars
# Current state As of Sept 14, 2026, Waymo has opened fully public (non-invite) robotaxi service in 15 distinct US metros: SF, LA, Phoenix, Atlanta, Austin, Miami, Dallas, Houston, San Antonio, Orlando, Nashville, Denver, San Diego, Tampa, and Las Vegas. This already sits at the very top edge of the 12-15 bucket, with 3.5+ months remaining before the Dec 31, 2026 resolution and several more cities (Detroit, Sacramento, DC, London) in active pre-launch pipeline that could push the count to 16+. # Timeline of key events - 2026-01: NHTSA/NTSB open investigations into school-bus-passing incidents (confirmed, Wikipedia) - 2026-02-24: Public launch in Dallas, Houston, San Antonio, Orlando — brings total to 10 metros (confirmed, TechCrunch) - 2026-02: Waymo raises $16B at $126B valuation (confirmed, Wikipedia) - 2026-06-18: Voluntary recall of ~3,900 vehicles for freeway construction-zone issue; analyst flags temporary expansion-velocity constraint (confirmed, CNBC) - 2026-07-08/19: Announces/begins rollout to San Diego, Las Vegas, Tampa, Denver (initially employee-only, then public) (confirmed, CNBC/Detroit News) - 2026-08-14: CPUC approves expansion across SF Bay Area, LA, and new service in Sacramento and San Diego; no firm launch date for Sacramento (confirmed, CBS/Engadget) - 2026-08-25: Announces Munich as third international market, targeting 2027 (confirmed, CNBC) - 2026-09-01: Denver, San Diego, Tampa go public — total 14 cities (confirmed, CNBC/CBS) - 2026-09-04: Reported as operating in 14 cities (confirmed, Repairer Driven News) - 2026-09-14: Las Vegas goes public — 15th city; Tokyo launch explicitly announced for 2027 (confirmed, Waymo blog/updates page) - Ongoing: DC blocked by city council inaction on legislation; Detroit/Michigan awaiting state regulatory approval; testing-only in Baltimore, Boston, Chicago, NYC, Seattle, Philadelphia, Pittsburgh, and others (reported, Understanding AI / Waymo updates page) # Event Will Waymo's publicly available ride-hailing service (Waymo One or Uber partner) operate in 12-15 distinct cities/regions as of Dec 31, 2026 11:59PM ET? # Outcomes to forecast Yes (12-15 cities) / No (outside that range, i.e., <12 or ≥16) # Kalshi market anchor No Kalshi-direct price returned (0 related Kalshi markets found for "Waymo"/"robotaxi"). Primary cross-market anchor is Polymarket's identical-ticker market: **current YES price 28.05%**, up +0.20% (7d) and +4.55% (30d), total volume ~$39.5K, historical range 0.35%-56.1% over 83 days. # Sub-question answers 1. **Current public city count**: 15 cities as of Sept 14, 2026 per Waymo blog and multiple outlets (SF, LA, Phoenix, Atlanta, Austin, Miami, Dallas, Houston, San Antonio, Orlando, Nashville, Denver, San Diego, Tampa, Las Vegas) — claude_news, repairerdrivennews, CNBC. 2. **Announced 2026-timeline additions**: Detroit (2026 target, pending Michigan approval), Sacramento (CPUC-approved Aug 2026, no firm date). **2027+ or vague**: Tokyo (explicit 2027), Munich (explicit 2027), London (testing, no date), DC (blocked, no date). 3. **Historical lag/slippage**: Waymo has repeatedly slipped from "announced" to "public" — e.g., Denver/San Diego/Tampa/Las Vegas were announced July 2026 but only went fully public Sept 2026 (~2 months lag); DC and Detroit have missed earlier informal timelines due to regulatory approval delays. 4. **Regulatory blockers**: DC council has stalled legislation needed for driverless commercial service (Understanding AI, Detroit News); Michigan/Detroit requires state regulatory approval (automotiveworld.com); London and Tokyo lack finalized public-launch regulatory clearance, with Tokyo explicitly deferred to 2027. 5. **Fleet/production constraints**: ~4,000 robotaxis in fleet as of mid-2026 (CNBC); June 2026 recall of ~3,900 vehicles for freeway-zone issue briefly constrained expansion velocity per analyst Grayson Brulte, though this appears resolved given continued Sept launches. 6. **Sibling buckets/Kalshi**: No Kalshi Waymo markets exist. No Polymarket sibling buckets (<12,16-19,20+) were found in the scan (0 related Polymarket markets returned) — only this ticker's own history available. 7. **Ambiguous counting**: Research/news consistently treats Bay Area, LA, and Phoenix as single regional units already (per Waymo's own city-based announcements), consistent with market's stated rule ("broader region ... counts as one"). Sacramento, Napa, Marin appear likely to be folded into "Bay Area" rather than counted separately, per CPUC approval framing. # Key facts (high-confidence, factual) 1. [Waymo blog/news] 15 public cities confirmed as of 2026-09-14. 2. [CNBC] Tokyo explicitly pushed to 2027 launch. 3. [CNBC] Munich (Germany) targeted for 2027, third international market. 4. [Understanding AI/Detroit News] DC lacks legal pathway; council delay ongoing. 5. [CBS/Engadget] CPUC approved Sacramento + San Diego + Bay Area/LA expansion Aug 2026; no confirmed Sacramento launch date. 6. [Wikipedia] Fleet ~3,871-4,000 vehicles as of mid-2026; $126B valuation post Feb 2026 raise. # Cross-market signals - Kalshi related: none found. - Polymarket (this ticker): 28.05% YES, mild upward drift, historically ranged 0.35%-56%, thin volume ($39.5K). - Sportsbook implied: N/A (not applicable to this event type). # Analyst opinions and speculation - Grayson Brulte (Autnmy AI): expansion velocity "fundamentally constrained" post-recall (June 2026), though subsequent launches suggest this was temporary. - Internal Monte Carlo model (code_execution): P(12-15) ≈ 40% under per-city counting vs. ≈74% under consolidated-metro counting; current evidence favors per-city counting (15 already reached), making the tighter/lower estimate more relevant. # Directional lean per outcome - **Yes (12-15)**: Currently sits exactly at top of range (15); supported if no further cities go public before Dec 31 (DC, Detroit, Sacramento, London all face real near-term blockers/vague dates). - **No (likely >15)**: Detroit (regulatory-pending but "2026 target"), Sacramento (already CPUC-approved, only needs operational rollout), and possible Bay Area sub-expansions create multiple plausible paths to 16+ before year-end, given ~3.5 months remaining and Waymo's demonstrated Sept 2026 launch cadence (3 cities in 2 weeks). - **No (<12)**: Essentially foreclosed — already at 15. # Gaps / unknowns - No official Waymo confirmation of exact "city" vs "region" counting for Sacramento/Napa/Marin relative to Bay Area. - No visibility into DC legislative timeline or Detroit/Michigan approval timeline specifics. - Limited Polymarket liquidity ($39.5K) limits confidence in market efficiency. # Calibration anchors - Polymarket YES 28.05% (primary anchor, thin volume). - Model-based estimate: ~35-45% under likely per-city convention (consistent with current 15-city count and multiple pending launches pushing past 15). - Precedent: Waymo has never regressed in city count; every recent quarter has added, not lost, cities — strong base-rate lean toward exceeding 15 rather than staying within 12-15 or falling below.
4. Forecasters Fable 5.1 + GPT-5.6 Sol · in parallel
claude-fable-5-1
52% conf
Yes 30%
No 70%
Waymo already sits at 15 public cities as of Sept 14, 2026, so 'Yes' requires zero additional public launches over the remaining ~3.5 months. Waymo's recent cadence (4 cities in Feb, 4 more Jul-Sept) and pending pipeline—Detroit (2026 target), Sacramento (CPUC-approved), London (testing, 2026 ambition), DC (blocked)—make at least one more launch more likely than not, though regulatory slippage in Michigan/DC and Sacramento possibly folding into the Bay Area region are real paths to staying at 15. The Polymarket anchor of 28% YES (thin, $39.5K volume) aligns with this reasoning; the brief's per-city Monte Carlo (~40%) is somewhat higher, so I settle at 30%.
gpt-5.6-sol
68% conf
Yes 34%
No 66%
The confirmed current count of 15 points toward Yes only if Waymo adds no separately counted market through year-end. Detroit's stated 2026 target and Sacramento's regulatory approval provide plausible paths to 16, although regulatory delays and ambiguity over whether Sacramento is separate from the Bay Area materially limit those paths. Tokyo and Munich are explicitly slated for 2027, while DC remains blocked, so a large overshoot is unlikely. With no Kalshi-direct price, I anchor on Polymarket's 28.05% YES and move modestly upward because the market is thin and the documented launch blockers make remaining at 15 somewhat more plausible than that price implies.
5. Devil's Advocate Sonnet 5 · red-team critique
1. Neither forecaster grapples with the sharp cadence evidence: "3 cities in 2 weeks" (Denver/San Diego/Tampa Sept 1, Las Vegas Sept 14) — this is a much faster recent pace than earlier in the year, and with 3.5 months left, this trend alone suggests high likelihood of at least one more launch, arguably justifying a lower Yes probability than ~30-34%. 2. Both forecasters ignore the tail risk of falling below 12 or ballooning to 16+ via multiple simultaneous launches (Detroit + Sacramento + London all landing before year-end), which the brief explicitly flags as "multiple plausible paths to 16+" — this scenario deserves more explicit weight than a single marginal-city framing implies. 3. Neither forecaster addresses the counting-convention ambiguity in depth despite the brief's Monte Carlo showing huge divergence (40% per-city vs 74% consolidated-metro) — they both default to per-city without justifying why Sacramento/Napa/Marin wouldn't fold into "Bay Area" the same way LA and Phoenix are already treated as single units, which could materially raise Yes probability if consolidated counting is more accurate. 4. Both anchor tightly to Polymarket's thin $39.5K-volume price (28.05%) despite explicitly acknowledging its low liquidity and citing the brief's own internal model estimate of 35-45%, yet neither moves substantially toward that internal estimate — they converge to 30-34%, effectively deferring to the weak market signal over their own reasoning. 5. Neither forecaster incorporates the "Waymo has never regressed in city count" base rate explicitly into confidence calibration, nor do they discuss how a launch failing to materialize (e.g., Detroit or Sacramento slipping to 2027, as Tokyo/Munich already have) could keep the count at exactly 15 — a scenario that seems at least as likely as one more city given DC's explicit blockage and Sacramento's "no firm launch date," which arguably supports a higher Yes probability than either gives. 6. Both forecasts cluster tightly (0.30 vs 0.34) despite one being "confidence 0.52" and the other "confidence 0.68" — neither explains why their confidence differs so much when their probability estimates and reasoning are nearly identical, suggesting the confidence scores are not well-calibrated to the actual uncertainty in counting conventions and regulatory timelines.
6. Aggregator Fable 5.1 · final calibrated forecast
33% (60% confidence)
Yes: 33% No: 67%
Waymo already counts 15 public metros, so Yes requires zero additional separately-counted launches over the remaining ~3.5 months; falling below 12 is effectively impossible, so this is a single-sided bet on the pipeline stalling. Detroit (stated 2026 target), Sacramento (CPUC-approved, likely counted as a distinct metro given its distance from the Bay Area), and London (testing with 2026 ambitions) each offer a plausible path to 16, and Waymo's recent cadence of batch launches makes at least one more before year-end more likely than not. Countervailing factors are real: Michigan approval is pending, Sacramento has no firm date, DC is legislatively blocked, and Waymo has repeatedly slipped announced timelines by months. Weighing the thin Polymarket anchor (~28%) against the brief's per-city model (~40%) and the documented blockers, I land near the forecasters' consensus at 33% Yes.
Pipeline Timing
Total pipeline time: 199.9s
Per-tool research timings shown in the Research section above.