DATA & QUANT
Structured, versioned event data
Event and contract data built for systematic research and data pipelines — not scraped, not silently recalculated. Point-in-time historical exports for backtesting are planned, not available yet.
Data and quant workflow
For quantitative research and data engineering teams: do the documented fields, authentication boundary and source availability fit the pipeline being designed?
- Map the required fields and response versions from the documentation before writing an adapter.
- Use the public synthetic sample to inspect request and response structure without treating it as venue data.
- Scope authenticated organization access and source rights separately, then retain provenance in downstream records.
Research output
A documented integration design based on exact response shapes, with source, version and access assumptions visible to the team.
Limitations to carry forward
Canonical routes require a signed-in organization session; production API-key transport is unavailable for them. Bulk point-in-time history is planned, not available. Source rollout and rights remain separate from code support.
Worked example
The shared canonical envelope and the separate Polymarket US on-demand workspace DTO are distinct documented response shapes. Field names and types are real; every displayed value is illustrative, not a live observation. US and Kalshi production collection are disabled.
| Field | Type | Example |
|---|---|---|
| data | T | { … } |
| asOf | string (ISO 8601) | 2026-09-02T14:32:00Z |
| sourceStatus | enum | DELAYED |
| sources | ProvenanceSource[] | [{ "source": "POLYMARKET", … }] |
| mappingVersion | string | null | map-2026-08@4 |
| methodologyVersion | string | intel-methodology-r1@1+intel-consensus-v0.1.1 |
Provenance
- Source
- POLYMARKET
- As of
- 2026-09-02 14:32 UTC
- Methodology version
- intel-methodology-r1@1+intel-consensus-v0.1.1
When the taxonomy moves past taxo_v1 to a new version, every affected record is explicitly recomputed, never silently rewritten. The docs page describes each field in full.
What you get
Shared canonical routes include entitled retained source records with their source-specific provenance; the dedicated Polymarket US workspace also has its own on-demand DTO. US and Kalshi production collection are currently disabled and no customer rights are implied.
| Capability | Status | Explore | Delivery |
|---|---|---|---|
| Structured event, contract, liquidity and signal records | Available | Not included | Production API |
| Event classification versioned as taxo_v1 | Available | Not included | Production API |
| Execution and liquidity math versioned as intel-execution-r1@1 | Available | Not included | Production API |
| Developer Sandbox keys, self-serve from your account settings | Available | Included | Developer Sandbox |
| Bulk history for backtesting | Planned | — | Historical exports |
| Kalshi records in the shared canonical data model, when enabled | Shared integration implemented; production disabled | — | Not delivered today |
Your evaluation
Three steps, and no commercial conversation until you have seen it against your own events.
Request access
Tell us your desk and your event set. We aim to reply within one business day.Scoping call
Thirty minutes on the events you actually cover and what a useful answer looks like.Institutional Evaluation
You evaluate Monitor against that event set before any commercial terms are discussed.
WORKING SAMPLE · SYNTHETIC DATA
Follow the research from observation to evidence.
Open Monitor, screen the universe, inspect contract terms, compare eligible outcomes and retain a research brief. Watchlists, saved views and adjustable workspaces keep the same event in context.
No account required for the sample. Its fictional records, local alerts and research stay separate from organization data. Portfolio scenarios are a bounded private beta; organization access still requires sign-in, plan and source permissions.
Tell us what you're building
Inspect the public synthetic API and its exact field definitions, then discuss authenticated organization data delivery for your research pipeline.
