HEDGE FUNDS
Event pricing, mapped to one canonical set of events
Research on event contracts that states what each mapping means and how far it has been verified, instead of leaving that judgement undocumented.
Hedge-fund research workflow
For event-risk and portfolio-construction researchers: is a contract's settlement proposition sufficiently aligned to include in the same research comparison?
- Define the event, outcome boundary, time window and intended research question.
- Inspect each contract's available terms, source rights and current relationship review state.
- Compare only eligible relationships, then keep the source, timing and assumptions with the memo.
Research output
A reviewed relationship state and source-linked research record that helps an analyst explain what was compared and what remains unresolved.
Limitations to carry forward
Cross-source analysis requires two currently entitled sources, a current human-reviewed mapping and eligible observations. US and Kalshi collection are disabled in the published profile; the public sample is synthetic.
Worked example
A mapping and its provenance as a research memo would cite them.
Canonical event: Policy rate decision, December meeting — cut of 25 bp or more. Mapped contracts: 3. Overall state: Unreviewed.
Contract at POLYMARKET: YES.
Contract at POLYMARKET: NO.
Contract at Second source: The same event on a second source. Source availability: Not entitled.
YES and NO: EXACT_COMPLEMENT, Verified.
- Source
- POLYMARKET
- As of
- 2026-09-02 14:32 UTC
- Quality
- DELAYED
- Methodology version
- intel-methodology-r1@1+intel-consensus-v0.1.1
- Taxonomy version
- taxo_v1
What you get
The same real-world event can have differently-worded contracts. The shared reference plane retains supported source records and makes reviewed mappings and provenance explicit; US and Kalshi production collection remains disabled.
| Capability | Status | Explore | Delivery |
|---|---|---|---|
| Named relationships between contracts on one canonical event | Available | Limited | Event workstation |
| A verification state on every mapping | Available | Limited | Event workstation |
| Provenance and version ids on every published figure | Available | Limited | Event workstation |
| The same records programmatically, for a research pipeline | Available | Not included | Production API |
| Cross-source comparison only when rights and a reviewed mapping permit it | Implemented; eligibility conditional | — | 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.
Talk to us about your research workflow
Review event terms, screen observations and retain the evidence behind a research conclusion. Request an evaluation for your organization’s authorized coverage.