Crene API, Developer Documentation
Public proof layer API.
Public read endpoints over the Crene corpus. No key required for current reads. Returns JSON.
https://api-get.crene.comCanonical platform stats: model leaderboard, category breakdown, active and resolved counts, broad corpus calibration metrics.
curl https://api-get.crene.com/api/events/crene_stats/curl https://api-get.crene.com/api/events/accuracy/curl https://api-get.crene.com/api/events/lang/en/?limit=20curl https://api-get.crene.com/api/clusters/curl https://api-get.crene.com/api/factors/health/curl https://api-get.crene.com/api/scenarios/The Probability endpoint, write access for arbitrary forward-looking questions, is available through private review access. Teams can request access below.
The Probability endpoint requires a key passed as the X-API-Key header. Read endpoints over the Crene corpus remain public.
Resolved outcomes are tied to named sources, including government data, central banks, SEC filings, primary financial reporting, and authoritative secondary reporting where appropriate. Full provenance is stored per event. How resolution works
/api/events/lang/en/Active binary forecasts. Four-model consensus across macro, rates, crypto, commodities, central banks, and policy events./api/events/accuracy/Resolved-event calibration summary. Brier scores, directional accuracy, confidence tiers, and domain breakdowns./api/events/crene_stats/Canonical platform stats: active and resolved counts, broad corpus calibration metrics, model leaderboard, and coverage.Read access over the Crene corpus. Returns JSON. No key required for current reads. Stable URLs.
View endpoints ↑Write access for arbitrary forward-looking questions starts with a private thesis review. Submit one real thesis first, then we scope API cadence and delivery around the review workflow.
Start with one thesis map →