Our mission

Make event-market data and portfolio analysis inspectable

Event-contract markets turn uncertain outcomes into tradable prices, but the infrastructure used to study those markets often stops at snapshots, wallet balances, or position-by-position P&L. That is not enough for teams that need to know which market state produced an observation or how related claims behave together.

Expreci is being built to close that gap. The data layer is designed to preserve ordered market updates, explicit gaps, and reconstruction provenance. The analytics layer is designed to treat positions as a portfolio of binary contingent claims and evaluate exposure, joint scenarios, probability paths, hedging considerations, and liquidity under stated assumptions.

The goal is not to replace judgment. It is to give researchers and market participants a clearer factual basis for applying their own judgment.

Why Expreci

Event contracts need more than a balance display

A portfolio can contain claims that share an underlying event, exclude one another, resolve on different dates, or carry very different liquidity. Meanwhile, historical order book research can fail when updates are missing, duplicated, reordered, or detached from a valid starting snapshot.

Expreci connects these problems. Reconstructable books provide the market-state evidence. Portfolio-level views provide the analytical context. Both are designed to expose uncertainty rather than hide it.

Examine the data layer Examine the analytics layer

Operating principles

How the product is being shaped

Evidence before convenience

Raw source records, sequence state, timestamps, gaps, and engine versions should remain inspectable. A convenient view is useful only when its evidence and validity boundary travel with it.

Portfolio before isolated positions

Event contracts can be dependent, mutually exclusive, nested, or staggered in time. Analysis should preserve those relationships instead of reducing the book to unrelated position marks.

Assumptions before conclusions

Scenario states, probability paths, valuation methods, and liquidity constraints should be explicit inputs. Outputs should describe their consequences without presenting one course of action as correct.

Boundaries before promises

Coverage, latency, completeness, and analytical capabilities should be claimed only when they can be measured and maintained. Beta status and known limits remain part of the product description.

Built with prospective users

Requirements should come from real workflows

Expreci is in Beta stage and is validating requirements from additional prospective users. Detailed workflow constraints, failure modes, and analytical questions determine what should be built first.

Designed for

Quantitative trading desks studying prediction-market microstructure
Crypto funds and family offices managing related event exposures
Market makers and liquidity providers evaluating order book state
Researchers and sophisticated traders working across multi-contract books

Evaluate the direction

Bring a specific data or portfolio problem

Tell us which market-data failure modes, portfolio relationships, scenario questions, or liquidity constraints matter to your work.

Share your requirements