Skip to content
Protocolzone Protocolzone

Data to Data · Financial & Insurance

Prediction market analysis with a graph of AI agents

We can see hundreds of event contracts but cannot analyse them consistently, and every analyst reads the evidence and the resolution rules differently.

This is a financial & insurance problem we approach through our Data to Data service line.

The problem

Prediction markets list event contracts on elections, economic releases, sport, weather and company news. Each one has a price that reads as a probability, and each one has resolution rules that decide what counts as yes.

A research team, a trading desk or an operator listing these markets faces the same issue: too many contracts to read carefully, analysts who weigh evidence differently, and no record of why a view was taken.

Why it’s hard

Three things make it harder than it looks:

  • Resolution rules. Many apparent mispricings are a misreading of what exactly will be judged, by whom and by when.
  • Evidence from many sources. News, structured data and the prices of related contracts each need different handling, and they arrive at different times.
  • Calibration. A probability is only useful if events given that probability happen about that often. Without scoring estimates against outcomes, overconfidence goes unnoticed.

And a price gap is not an edge until fees, spread and liquidity have been counted.

How we approach it

We build the analysis as a LangGraph graph:

  1. Read the resolution rules. An agent extracts what counts as yes, the source of truth and the deadline, and flags ambiguity.
  2. Gather evidence in parallel. Separate agents for news, structured data and related contracts, fanned out and joined in one shared state.
  3. Estimate the probability, with reasons. The estimate carries the evidence it used, so a reviewer can challenge a reason rather than a number.
  4. Compare with the price in code. Net of fees and spread. With no gap, the result is logged and the run ends.
  5. Analyst review. With a gap, the graph pauses through an interrupt for a person to accept or reject the reasoning.
  6. Calibrate. Every resolved contract scores the estimate that preceded it, and the scores feed back into how much weight the graph gives each source.

What we would not do: let the graph act on a gap without review, trust a single model’s estimate without its evidence, or describe the output as investment advice.

What it takes

  • Access to the contracts, prices and resolution rules you work with, through the market’s published interfaces.
  • The evidence sources you trust, and the ones you do not.
  • A decision on what the output is for: research notes, pricing input for an operator, or a queue for analysts.
  • Clarity on the licence you operate under. That shapes what the system may do.

Where this has been done

This is a capability. The probability modelling discipline behind it is delivered work: separating the prediction from the position, which we explain in Predicting an outcome and staking on it are two problems, and backtesting with point in time data. The same agent graph pattern is being built into AnkEDGE. See Agentic AI and LangGraph for other industries.

Position on this page

Evidence

Implementation approach

Industry

Financial & Insurance

Written for

Head of Trading, Head of Product, CTO

Outcome

Every contract analysed the same way, with the rules read first, evidence and reasons recorded, price compared after fees, and estimates scored against outcomes.

Questions we get asked

Straight answers.

What does a prediction market price mean?
The price of an event contract reads as the market's probability that the event happens. The analytical question is whether that probability is right and whether any difference survives fees, spread and resolution risk.
Why use several agents instead of one model?
Because the steps fail differently. Reading resolution rules, gathering news, pulling structured data and comparing related contracts are separate jobs that can run in parallel, be tested separately and be audited separately. LangGraph fans them out and joins the evidence into one state.
Are prediction markets legal?
It depends on the jurisdiction and the licence. Some regulators treat event contracts as financial products and others as gambling. Any build starts from what the operator or firm is licensed to do.
Will this make money?
We make no claim about returns. Usually the analysis finds no edge, and the system records that. The value is consistent, explainable analysis and an honest measure of how well calibrated the estimates are.

Read next

Related work.

Other use cases

Is this your problem?

Bring the constraint that makes your version harder than this one. That is the part worth an hour.