Loading shell…
OtherExpires Jun 30, 2026

Will Waymo launch in Detroit by June 30 2026?

Probability

12¢

1h

-0.1pp

24h

+2.1pp

24h Vol

$5.04

Liquidity

$3.3K

Probability (last 7 days)

+1.1pp 7d
Apr 18, 2026, 07:00Apr 25, 2026, 06:18
updated 0s ago·src:Polymarket CLOB

Why did it move?

 

Heuristic summary, generated from the public market metrics above: probability movement, volume, liquidity, spread, signals, and resolution status.

Timeline — news, trades, signals, price moves

AllTradesSignalsPrice
  • 0s agoResolve

    Market resolves in 1577.7h

    LOW
  • 06:19Signal

    Signal · Resolution risk

    Expires in 1578h with open resolution ambiguity.

    LOW
updated 0s ago·src:Polymarket CLOB·Polymarket Data

Active signals

Recent Trades

No recent trades visible from the Data API for this market.

updated 0s ago·src:Polymarket Data

Market Description

This market will resolve to “Yes” if Waymo begins offering its ride-hailing service to the general public within the listed city by June 30, 2026, 11:59 PM ET. Otherwise this market will resolve to "No". Any taxi service available to the general public which operates without a human driver actively controlling the vehicle will count, regardless of membership or other financial restrictions. A qualifying launch requires the general public be able to hail a Waymo vehicle within the listed city \ through the Waymo One app or another official Waymo platform (such as a dedicated website or integrated partner app like Uber). Limited pilot programs, internal employee testing, or invite-only service will not qualify. The primary resolution source is official information from Waymo (see: https://waymo.com/rides/c), however a consensus of credible reporting may also be used.

Resolution & Risk

LOW risk
End date
Jun 30, 2026
UMA status
n/a
Resolution source
credible reportingNews consensusextracted · medium
Market type
Binary
  • No obvious resolution-risk signals in metadata.
Read full market rules on Polymarket

Alerts

¢
Deliver

In-app banners work now. Email / Telegram / Discord delivery lands when the backend alert dispatcher ships (needs RESEND_API_KEY + per-user webhook storage).