What you get
Request?expand=causal on any analysis or signal endpoint:
Factor anatomy
EachCausalFactor represents one driver of the outcome:
| Field | Type | Description |
|---|---|---|
claim | string | What this factor asserts |
direction | string | "supports_yes", "supports_no", or "neutral" |
weight | float (0-1) | Relative importance — weights across factors sum to ~1.0 |
confidence | float (0-1) | How confident Rekko is in this specific factor |
prior | float (0-1) | Base rate probability before evidence |
posterior | float (0-1) | Updated probability after incorporating evidence |
evidence | string[] | Key evidence supporting this factor |
How it works
- Factor identification — The research pipeline identifies 3-7 independent causal drivers of the outcome
- Prior estimation — Each factor starts with a base rate (prior) drawn from historical patterns
- Evidence gathering — Deep web research collects relevant evidence for each factor
- Bayesian update — Each factor’s prior is updated to a posterior based on the evidence strength
- Weighted aggregation — Factors are combined using their weights to produce the overall probability
method field indicates the aggregation approach:
| Method | Description |
|---|---|
weighted_bayesian | Standard weighted Bayesian combination (default) |
linear | Simple weighted average of posteriors |
log_odds | Log-odds weighted combination |
Why this matters
Most prediction market APIs just give you a price. Rekko gives you the reasoning chain:- Audit the logic — See exactly which factors drive the estimate and whether you agree
- Identify blind spots — Check if important factors are missing from the decomposition
- Track changes — When you re-analyze later, see which factors shifted and why
- Override confidently — If you have domain expertise on a specific factor, you can judge whether the overall estimate is too high or too low
Requesting causal decomposition
Add?expand=causal to any analysis or signal endpoint: