yes Toronto,yes San Francisco,yes Phoenix
| Platform | Yes | No | Volume | Last seen | Link |
|---|---|---|---|---|---|
| Kalshi | — | — | — | 07:23 UTC | View → |
| Kalshi | — | — | — | 11:48 UTC | View → |
| Kalshi | — | — | — | 11:49 UTC | View → |
| Kalshi | — | — | — | 07:23 UTC | View → |
| Kalshi | — | — | — | 08:39 UTC | View → |
| Kalshi | — | — | — | 21:19 UTC | View → |
| Kalshi | — | — | — | 07:23 UTC | View → |
| Kalshi | — | — | — | 08:27 UTC | View → |
| Kalshi | — | — | — | 07:25 UTC | View → |
| Kalshi | — | — | — | 07:25 UTC | View → |
| Kalshi | — | — | — | 07:23 UTC | View → |
| Kalshi | — | — | — | 01:12 UTC | View → |
| Kalshi | — | — | — | 00:45 UTC | View → |
| Kalshi | — | — | — | 07:32 UTC | View → |
| Kalshi | — | — | — | 06:56 UTC | View → |
| Kalshi | — | — | — | 07:23 UTC | View → |
| Kalshi | — | — | — | 07:23 UTC | View → |
| Kalshi | — | — | — | 12:28 UTC | View → |
| Kalshi | — | — | — | 07:32 UTC | View → |
| Kalshi | — | — | — | 01:03 UTC | View → |
| Kalshi | — | — | — | 07:30 UTC | View → |
| Kalshi | — | — | — | 00:39 UTC | View → |
| Kalshi | — | — | — | 11:48 UTC | View → |
| Kalshi | — | — | — | 08:22 UTC | View → |
| Kalshi | — | — | — | 10:33 UTC | View → |
| Kalshi | — | — | — | 11:48 UTC | View → |
| Kalshi | — | — | — | 09:42 UTC | View → |
| Kalshi | — | — | — | 14:40 UTC | View → |
| Kalshi | — | — | — | 07:59 UTC | View → |
| Kalshi | — | — | — | 16:07 UTC | View → |
| Kalshi | — | — | — | 14:43 UTC | View → |
| Kalshi | — | — | — | 09:44 UTC | View → |
| Kalshi | — | — | — | 07:59 UTC | View → |
| Kalshi | — | — | — | 09:44 UTC | View → |
| Kalshi | — | — | — | 10:44 UTC | View → |
| Kalshi | — | — | — | 08:12 UTC | View → |
| Kalshi | — | — | — | 00:42 UTC | View → |
| Kalshi | — | — | — | 14:33 UTC | View → |
| Kalshi | — | — | — | 09:43 UTC | View → |
| Kalshi | — | — | — | 08:42 UTC | View → |
| Kalshi | — | — | — | 08:12 UTC | View → |
| Kalshi | — | — | — | 19:27 UTC | View → |
| Kalshi | — | — | — | 00:32 UTC | View → |
| Kalshi | — | — | — | 00:25 UTC | View → |
| Kalshi | — | — | — | 10:34 UTC | View → |
| Kalshi | — | — | — | 14:40 UTC | View → |
| Kalshi | — | — | — | 10:36 UTC | View → |
| Kalshi | — | — | — | 00:46 UTC | View → |
| Kalshi | — | — | — | 00:32 UTC | View → |
| Kalshi | — | — | — | 08:14 UTC | View → |
| Kalshi | — | — | — | 00:42 UTC | View → |
What do these odds mean?
Cross-platform data for yes Toronto,yes San Francisco,yes Phoenix is still being collected.
How to read cross-platform spreads
When two platforms price the same event meaningfully differently, it usually means one of three things: liquidity is thin on one side, fee structures are pushing a spread, or traders on one platform have information the other lacks. Spreads larger than 5 percentage points on events with over $50K in volume often resolve toward the higher-volume platform's price.
About this data
Beeks.ai aggregates prediction market data from Polymarket, Kalshi, and Manifold. Updates run every minute. Consensus probability is a volume-weighted average across all matched markets. Historical snapshots are stored for calibration analysis.
News & context
Your edge calculator
Enter your own probability estimate to see expected value and recommended position size using the Kelly Criterion.