Events vs Markets

Two-level hierarchy

EventGraph organizes all prediction data in two layers:

Event  (topic group)
  └── Market 1  (e.g. "Yes — will happen")
  └── Market 2  (e.g. sub-outcome A)
  └── Market N  ...

An Event is the top-level topic — e.g. “2026 US Presidential Election”.
A Market is a tradeable binary contract within that event — e.g. “Will Candidate X win?”. Simple binary questions on Polymarket may have just 1 market per event.
Kalshi events typically have many sub-markets (one per candidate or outcome).

Key event fields

Field	Type	Description
`event_id`	string	Platform-specific slug or ID
`platform`	string	`polymarket` \| `kalshi` \| `limitless` \| `opiniontrade`
`category`	string	`crypto`, `politics`, `sports`, `finance`, `other`
`total_volume`	number	Lifetime trading volume in USD
`volume_24h`	number	Rolling 24-hour trading volume
`market_count`	number	Number of sub-markets in this event
`status`	string	`open` \| `closed` \| `resolved`
`end_time`	number	Unix timestamp of resolution date
`link`	string	Direct URL to the event on the source platform

Key market fields

Field	Type	Description
`market_id`	string	Platform-specific market ID or ticker
`yes_price`	number	Implied YES probability (0.0 – 1.0)
`no_price`	number	`1 - yes_price`
`volume_total`	number	Lifetime volume for this market
`volume_24h`	number	24-hour rolling volume
`token_id`	string	On-chain token ID (Polymarket only)
`source_url`	string	Deep-link directly to this market
`status`	string	`open` \| `closed` \| `resolved`

Get Started

Core Concepts

Two-level hierarchy

Key event fields

Key market fields

Get Started

Core Concepts

​Two-level hierarchy

​Key event fields

​Key market fields

Two-level hierarchy

Key event fields

Key market fields