Loading shell…
AIExpires Apr 30, 2026

Will Claude 5 be released by April 30, 2026?

Probability

1h

+0.0pp

24h

-0.1pp

24h Vol

$3.8K

Liquidity

$37.8K

Probability (last 7 days)

-0.3pp 7d
Apr 18, 2026, 15:00Apr 25, 2026, 11:21
updated 0s ago·src:Polymarket CLOB

Why did it move?

 

Heuristic summary, generated from the public market metrics above: probability movement, volume, liquidity, spread, signals, and resolution status.

Timeline — news, trades, signals, price moves

AllTradesSignalsPrice
  • 0s agoResolve

    Market resolves in 108.6h

    LOW
  • 11:21Signal

    Signal · Resolution risk

    Expires in 109h with open resolution ambiguity.

    LOW
updated 0s ago·src:Polymarket CLOB·Polymarket Data

Active signals

Recent Trades

No recent trades visible from the Data API for this market.

updated 0s ago·src:Polymarket Data

Market Description

This market will resolve to "Yes" if Anthropic's Claude 5 model is made available to the general public by April 30, 2026, 11:59 PM ET. Otherwise, this market will resolve to "No." For this market to resolve to "Yes," Claude 5 must be launched and publicly accessible, including via open beta or open rolling waitlist signups. A closed beta or any form of private access will not suffice. The release must be clearly defined and publicly announced by Anthropic as being accessible to the general public. Claude 5 refers to a product explicitly named Claude 5 (e.g. Claude 5.0 would count), or one that is recognized as a successor to Claude 4, similar to the progression from Claude 2 to Claude 3. Products labeled as Claude 4.5 or similar will not count for this market's resolution. The primary resolution source for this market will be official information from Anthropic, with additional verification from a consensus of credible reporting.

Resolution & Risk

LOW risk
End date
Apr 30, 2026
UMA status
n/a
Resolution source
Not specified in metadata
Market type
Binary
  • No obvious resolution-risk signals in metadata.
Read full market rules on Polymarket

Alerts

¢
Deliver

In-app banners work now. Email / Telegram / Discord delivery lands when the backend alert dispatcher ships (needs RESEND_API_KEY + per-user webhook storage).