SimpleFunctions

Detroit, MI · Will Waymo operate ride-hailing

Detroit, MI is priced at 63¢ on Kalshi. Current book: 57¢ bid, 63¢ ask, 6¢ spread. This outcome ranks #5 of 10 inside Will Waymo operate ride-hailing.

Price history

63¢ current

+61¢
0¢25¢50¢
May 13, 2026May 20, 2026

Contract brief

If Waymo is operating commercial autonomous vehicle ride-hailing services available to the general public within Detroit, MI before Jan 1, 2027, then the market resolves to Yes.

Outcome

Detroit, MI

Rank

#5 of 10

Leader

San Diego, CA 79¢

Range

27¢-79¢

Family volume

$33

Identifier

KXWAYMOCITY-26DEC-DET

May 26, 2026, 7:08 PM UTC · 18m ago

Implied probability

63¢
Latest venue quote
May 26, 2026, 7:08 PM UTC · 18m ago

Bid

57¢

Ask

63¢

Spread

24h volume

$8

Family rank

#5 of 10

10 outcomes · Will Waymo operate ride-hailing

Closes

Dec 31, 2026

Family volume

$33

Orderbook snapshot

57 / 63¢

Kalshi
6¢ spread
BidSize
57¢5
56¢500
50¢101
26¢45
25¢759
AskSize
63¢501
70¢100
75¢8
88¢55
89¢200

Contract terms

What resolves this market.

YES condition

If Waymo is operating commercial autonomous vehicle ride-hailing services available to the general public within Detroit, MI before Jan 1, 2027, then the market resolves to Yes.

Venue

Kalshi

Closes

Dec 31, 2026

Identifier

KXWAYMOCITY-26DEC-DET

SF Signal
SF Index
110.55
Regime
neutral

Indicators

Yield, cliff risk, volatility, and regime.

IY (Yes)

125.8%

IY (No)

221.1%

Adj IY

111%

CRI

1

Overround

4.0%

Regime

neutral

Score

0.432

Observability

medium

Event type

financial

Full indicator table

125.8%
221.1%
Adj IY
111%
1
Overround
4.0%

Odds pages

Related prediction questions

Browse odds

Related readings

Matched from SimpleFunctions blog, opinions, technical guides, concepts, and learn pages.

Browse library
Blogmarkets

Kalshi vs Polymarket: Which Prediction Market Should You Trade?

In-depth comparison of Kalshi and Polymarket for prediction market traders. Regulatory structure, liquidity, fees, API tooling, and cross-venue trading with SimpleFunctions.

Blogmarkets

Prediction Market Orderbook Analysis: Reading Depth, Spread, and Liquidity

How to read prediction market orderbooks. Binary settlement, spread-as-percentage, depth asymmetry, executable edge calculation, and cross-venue arbitrage analysis.

Technicalguide

Kalshi vs Polymarket: A Developer's Comparison of APIs, Orderbooks, and Liquidity

Data-driven comparison of Kalshi and Polymarket APIs, orderbooks, rate limits, and liquidity. Code examples for building on both prediction markets.

Opinionanalysis

Liquidity Availability Is the Real Edge in Prediction Markets

Implied yield, cliff risk, and overround all describe what to trade. Liquidity Availability Score describes whether the orderbook can absorb the trade. Why LAS is the indicator that decides who actually books P&L.

Opinionanalysis

Implied Yield vs Raw Probability: Why Bond-Adjacent Prediction Markets Need a Different Lens

Why fixed-income-adjacent prediction-market contracts need to be priced in implied yield, not raw probability, with two real Kalshi Fed-decision contracts as a case study.

Blogtech

MCP Servers for Prediction Markets: Connect Claude Code to Kalshi and Polymarket

Connect Claude Code, Cursor, or Cline to Kalshi and Polymarket prediction markets via MCP. One-line setup, 18 tools, real-time market data for AI agents.

SimpleFunctions context

Index, screen, query, and monitor.

Open index

How we compute these odds

SimpleFunctions aggregates live prediction-market contracts from Kalshi and Polymarket. Each slug groups contracts that resolve on the same underlying event, identified by venue event_id.

For binary slugs, the headline probability is the liquidity-weighted mid-price across all bound contracts. For multi-outcome slugs (e.g. elections with 3+ candidates), the headline is the leader’s price; we never arithmetically average disjoint outcomes — that would produce a number with no real-world meaning.

Snapshots refresh every 5 minutes during market hours; daily aggregates are computed at 04:00 UTC. The 30-day sparkline is drawn from per-ticker daily means stored in market_indicator_daily; 24h delta and movement events are derived from the same source.