Markets API

Proposals

• GET /v1/eventa/proposals — Eventa proposals with filters: language, region, cluster country, proposal_kind, min_impact, min_confidence, min_interest, status
• GET /v1/markets/proposals — List proposals; filter by status (pending_review, approved, rejected)
• POST /v1/markets/proposals — Create a proposal (question, expiry, resolution_sources, source_article_ids, plus optional Eventa fields: cluster_id, proposal_kind, direction_hint, impact/confidence/interest scores, language, region, assets). Stored as pending_review.

Built for automated pipelines: workers read Live/News, POST hypotheses here; humans approve or reject in the client portal. Human developers use the same flows.

Venue catalogs & merged events

GET /v1/markets/polymarket and GET /v1/markets/kalshi are the canonical venue lists (Gamma snapshot and Kalshi Trade API import when enabled). To surface those rows inside the events feed, use include_polymarket=true or include_kalshi=true on GET /v1/events/latest—field-level detail lives on the Events API page so we do not duplicate it here.

Use cases

Prediction platforms that need proposal intake and Polymarket-style data. Proposals stay in review until a human approves or rejects—no automated listing.