SimpleFunctions

Nick Begich receive at least 55% of the popular vote in the Alaska at-large congressional district primary

At least 55% is priced at 5¢ on Kalshi. Current book: 0¢ bid, 12¢ ask, 12¢ spread. This outcome ranks #4 of 6 inside Will Nick Begich receive at least.

Price history

5¢ current

13¢
0¢10¢20¢
Aug 14, 2026Aug 19, 2026

Contract brief

If the certified percentage of the popular vote received by Nick Begich in the Alaska at-large congressional district primary is 55% to 100%, inclusive of both endpoints, then the market resolves to Yes.

Outcome

At least 55%

Rank

#4 of 6

Leader

At least 35% 99¢

Range

1¢-99¢

Family volume

$4

Identifier

KXVOTEPRIMARY-AKPRIMARY26MAY19NBEG-55

Aug 21, 2026, 5:38 AM UTC · 11m ago

Implied probability

5¢
Latest venue quote
Aug 21, 2026, 5:38 AM UTC · 11m ago

Bid

Ask

12¢

Spread

12¢

Reported volume

$2K

Family rank

#4 of 6

6 outcomes · Will Nick Begich receive at least

Closes

Aug 18, 2027

Family volume

$4

Orderbook snapshot

0 / 12¢

Kalshi
12¢ spread
BidSize
AskSize
12¢237
13¢30
15¢110
34¢15
35¢500

Contract terms

What resolves this market.

YES condition

If the certified percentage of the popular vote received by Nick Begich in the Alaska at-large congressional district primary is 55% to 100%, inclusive of both endpoints, then the market resolves to Yes.

Venue

Kalshi

Closes

Aug 18, 2027

Identifier

KXVOTEPRIMARY-AKPRIMARY26MAY19NBEG-55

SF Signal
SF Index
956.95
Regime
neutral

Indicators

Yield, cliff risk, volatility, and regime.

IY (Yes)

1913.9%

IY (No)

5.3%

Adj IY

957%

CRI

19

Overround

-0.1%

Regime

neutral

Score

0.5

Full indicator table

1913.9%
5.3%
Adj IY
957%
19
Overround
-0.1%

Related readings

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

Browse library
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.

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.

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.