Toronto to win Miami vs Toronto
Toronto is priced at 60¢ on Kalshi. Current book: 59¢ bid, 60¢ ask, 1¢ spread. This outcome ranks #1 of 2 inside Miami vs Toronto Winner.
Price history
60¢ current
+1¢Contract brief
If Toronto wins the Miami vs Toronto professional baseball game originally scheduled for May 25, 2026 at 7:07 PM EDT, then the market resolves to Yes.
Outcome
Toronto
Rank
#1 of 2
Leader
Toronto 59¢
Range
40¢-59¢
Family volume
$64K
Identifier
KXMLBGAME-26MAY251907MIATOR-TOR
May 25, 2026, 5:08 PM UTC · 18m ago
Implied probability
Bid
59¢
Ask
60¢
Spread
1¢
24h volume
$50K
Family rank
#1 of 2
2 outcomes · Miami vs Toronto Winner
Closes
May 28, 2026
Family volume
$64K
Orderbook snapshot
59 / 60¢
Contract terms
What resolves this market.
YES condition
If Toronto wins the Miami vs Toronto professional baseball game originally scheduled for May 25, 2026 at 7:07 PM EDT, then the market resolves to Yes.
Venue
Kalshi
Closes
May 28, 2026
Identifier
KXMLBGAME-26MAY251907MIATOR-TOR
Event family
Miami vs Toronto Winner.
The same race as a probability stack: rank, volume, and where this contract sits against the other outcomes.
Total volume
$64K
Outcomes
2
Highest price
Toronto 59¢
Current share
76%
Browse this series
Indicators
Yield, cliff risk, volatility, and regime.
Regime
neutral
Score
0.5
Full indicator table
Odds pages
Related prediction questions
Related readings
Matched from SimpleFunctions blog, opinions, technical guides, concepts, and learn pages.
Kalshi vs Polymarket: Mechanics, Fees, Regulation, Liquidity (2026)
Side-by-side comparison of Kalshi and Polymarket in 2026. Fee math, calibration data, withdrawal speed, and a decision tree for picking the right venue.
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.
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.
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.
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.
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.
SimpleFunctions context
Index, screen, query, and monitor.
Prediction Market Index
Market-wide volatility, geo risk, breadth, and activity around this contract.
Market Screener
Filter adjacent contracts by volume, expiry, IY, CRI, venue, and theme.
Event Probability API
Read 60% as a structured event probability object for agents and apps.
Realtime Data API
Prices, orderbooks, movement, heat, and liquidity indicators across venues.
World State API
Compact market-aware context packets for agent sessions and scheduled refresh.
Hedging Workflows
Map a thesis or exposure to candidate event markets and monitoring paths.
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.