Data & Methodology
Effective and last updated: July 28, 2026
1. Source policy
Runtime market data is obtained from official or explicitly configured sources. EventCap labels implementation capability separately from live connection status. The presence of code for an integration does not mean credentials, licenses, or fresh data are available.
2. Freshness and completeness
Timestamps, source status, collection runs, and retained snapshots are used to communicate freshness. API outages, rate limits, closed markets, missing order books, or absent credentials can reduce completeness. A blank or unavailable value is preferable to fabricated data.
3. Market matching
Cross-market relationships may be exact and manually verified, structurally similar but unverified, or candidates requiring review. Titles alone are not sufficient. Close time, resolution source, outcome meaning, eligibility, and settlement language should be compared.
4. Price gaps and execution
A raw price gap is not necessarily executable. Execution views may account for available depth, spread, fees, direction, partial fills, and quote age. Even a modeled positive edge can disappear before both legs execute.
5. Confidence indicators
Confidence describes source completeness, freshness, verification state, and available evidence. It is not a forecast probability and does not guarantee that a market outcome or strategy is correct.
6. Historical performance
Track-record views depend on retained signals, checkpoints, resolution status, and consistent evaluation rules. Selection effects, changing market conditions, incomplete history, and small samples can make historical metrics misleading.
7. Corrections
Data defects or matching errors may be corrected as new official information becomes available. Questions or reproducible issues may be sent to support@eventcap.xyz with the market URL, timestamp, and observed discrepancy.