Data status

Overview

This page reports the state of the market data behind the feed. The live status panel above is generated from the same public feed endpoint that powers the site, so it reflects real backend state rather than a hand-written claim.

Source coverage

  • Polymarket — ingested from Polymarket's public API. Coverage is limited to active, non-expired markets above our volume threshold.
  • Kalshi — ingested from Kalshi's public API, including series-level events. Coverage is limited to active, non-expired contracts above our volume threshold.

A venue is not shown as unavailable simply because a single market is missing: markets can be excluded by volume thresholds, expiry filters or matching safety checks. Per-source last-verified timestamps are not currently published separately from the overall refresh timestamp.

Refresh target

Pricing refresh is scheduled every three minutes. Deeper ingest, matching, scoring, and rebuild work runs separately and does not share that public pricing freshness target. Upstream outages, slow venue responses, or pipeline failures can extend the gap between successful refreshes.

Known limitations

  • Matching between venues is automated and can be wrong. A pair labelled Similar Market is not a like-for-like comparison.
  • Prices can be stale. What you see is the last successful snapshot, not a live quote.
  • Settlement rules differ by venue, even for contracts that read identically.
  • Thin markets can show a mid-price far from where a real order would fill, and liquidity figures are not published by every venue.
  • Always open the linked venue and verify price, liquidity, fees and resolution rules before acting.

Safety statement

Prediction Pantheon is a read-only market-information service. It does not custody funds, execute trades, accept deposits, or request private keys or seed phrases. Displayed prices are venue-derived market-implied values, not Prediction Pantheon forecasts. Always verify the linked venue's live price, liquidity, fees, and resolution rules before acting.

Machine-readable status

The same status values are published in the public feed response at the ai-feed endpoint documented in /llms.txt and /.well-known/ai-feed.json, as data_status, last_successful_refresh, data_age_seconds and refresh_target_seconds.

Frequently asked questions

What does delayed mean?

The last successful refresh is older than our expected window, so prices on the site may lag the venue. The venue's own page remains authoritative.

Why is a market I expect missing?

Markets can be excluded because they are expired, below our volume threshold, or failed a matching safety check. Missing markets are not necessarily an outage.

Keep reading