Amanda · KXHURRICANENAMES-26DEC01EPAC
Amanda is priced at 25¢ on Kalshi. Current book: 0¢ bid, 97¢ ask, 97¢ spread. This outcome ranks #4 of 4 inside KXHURRICANENAMES-26DEC01EPAC.
Price history
25¢ current
−5¢Contract brief
If a storm named Amanda is a storm categorized as a hurricane in the Eastern Pacific between May 15, 2026 and December 01, 2026, then the market resolves to Yes.
Outcome
Amanda
Rank
#4 of 4
Leader
Winnie 98¢
Range
25¢-98¢
Family volume
$27
Identifier
KXHURRICANENAMES-26DEC01EPAC-AMA
Jun 8, 2026, 5:08 AM UTC · 10m ago
Implied probability
Bid
0¢
Ask
97¢
Spread
97¢
24h volume
$26
Family rank
#4 of 4
4 outcomes · KXHURRICANENAMES-26DEC01EPAC
Closes
Dec 1, 2026
Family volume
$27
Orderbook snapshot
0 / 97¢
Contract terms
What resolves this market.
YES condition
If a storm named Amanda is a storm categorized as a hurricane in the Eastern Pacific between May 15, 2026 and December 01, 2026, then the market resolves to Yes.
Venue
Kalshi
Closes
Dec 1, 2026
Identifier
KXHURRICANENAMES-26DEC01EPAC-AMA
Event family
KXHURRICANENAMES-26DEC01EPAC.
The same race as a probability stack: rank, volume, and where this contract sits against the other outcomes.
Total volume
$27
Outcomes
4
Highest price
Winnie 98¢
Current share
96%
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: 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: 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.
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.
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.
Maker / Taker Regime in Prediction Markets: How to Read the Orderbook State
Three regime states (maker-dominated, taker-dominated, neutral) and how to read which one a Kalshi or Polymarket contract is in. Strategy follows regime, not thesis.
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 25% 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.