SimpleFunctions

Denver, CO · Will Waymo operate ride-hailing

Denver, CO is priced at 88¢ on Kalshi. Current book: 84¢ bid, 88¢ ask, 4¢ spread. This outcome ranks #3 of 16 inside Will Waymo operate ride-hailing.

Price history

88¢ current

+4¢
75¢100¢
Aug 18, 2026Sep 12, 2026

Contract brief

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

Outcome

Denver, CO

Rank

#3 of 16

Leader

Las Vegas, NV 93¢

Range

2¢-93¢

Family volume

$1K

Identifier

KXWAYMOCITY-26DEC-DEN

Sep 17, 2026, 10:38 PM UTC · 24m ago

Implied probability

88¢
Latest venue quote
Sep 17, 2026, 10:38 PM UTC · 24m ago

Bid

84¢

Ask

88¢

Spread

24h volume

$55

Family rank

#3 of 16

16 outcomes · Will Waymo operate ride-hailing

Closes

Dec 31, 2026

Family volume

$1K

Orderbook snapshot

84 / 88¢

Kalshi
4¢ spread
BidSize
84¢203
83¢301
82¢189
81¢200
67¢1.0K
AskSize
88¢20
89¢200
93¢10
94¢25
95¢29

Contract terms

What resolves this market.

YES condition

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

Venue

Kalshi

Closes

Dec 31, 2026

Identifier

KXWAYMOCITY-26DEC-DEN

SF Signal
SF Index
915.28
Regime
neutral

Indicators

Yield, cliff risk, volatility, and regime.

IY (Yes)

66.4%

IY (No)

1830.6%

Adj IY

915%

CRI

5

Overround

3.6%

Regime

neutral

Score

0.432

Observability

medium

Event type

financial

Full indicator table

66.4%
1830.6%
Adj IY
915%
5
Overround
3.6%

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.