Prediction market APIs — observational vs product APIs
A reviewed table of data freshness models, auth expectations, and what each surface is for — without dumping market URL inventories.
Comparison table
| Surface | Auth | Freshness model | Primary use |
|---|---|---|---|
| Venue public/dev APIs | Vendor-specific | Live upstream | Trading apps / research scripts |
| Insydr SEO HTML pages | None | Precomputed snapshots + observation time | Public discovery / citation |
| Insydr product API | API key / session | Product freshness SLAs | Customer integrations |
| Sitemap / robots / llms.txt | None | Catalog + editorial publish state | Crawler / assistant discovery |
Scope
Teams often confuse venue public APIs, Insydr HTML pages, and Insydr's authenticated product API. This comparison keeps those roles separate.
Insydr public pages
HTML market and hub pages are server-rendered from precomputed snapshots. They do not call venue APIs on the request path. Observation times travel with prices.
Product API
Authenticated Insydr API access is for customers integrating signals and market detail into their own stack. It is not a substitute for Search Console or sitemap discovery.
Venue APIs
Polymarket and Kalshi expose their own developer surfaces with their own rate limits and schemas. Insydr ingest uses those upstream; public SEO pages do not.