Skip to main content
SimpleFunctions is prediction-market infrastructure for desks, pods, and agents: market intelligence, calibrated feeds, monitoring, risk review, and execution workflows. The desk/pod pilot is a focused way for an institutional team to evaluate where prediction-market state belongs in its workflow. It starts with one real operating question and one real consumer: a trading desk, market-making team, quant pod, data platform, product team, or internal agent. The goal is not another generic dashboard. The goal is to find the part of the workflow where prediction-market state becomes useful enough to route, monitor, or automate.

​
Why now

Prediction markets are moving from novelty to market structure. They now sit at the intersection of macro, politics, crypto, weather, sports, litigation, private markets, and real-time sentiment. For institutions, the hard part is not finding a venue. The hard part is turning fragmented event markets into a usable operating layer:
  • Which event probabilities matter to this desk or pod?
  • What changed, and was the move meaningful?
  • Is the signal usable as market intelligence, alternative data, or execution input?
  • Where should a human review, risk gate, or approval step sit?
  • Which parts should be consumed by internal tools or AI agents?
SimpleFunctions is built for that layer above the venues.

​
Pilot shape

The pilot is intentionally narrow. It can begin read-only, with no platform migration and no sensitive position data required for the first pass.

​
Who it is for

​
What you get

A good pilot produces concrete artifacts that can be routed internally: The output is designed to help the team decide whether SimpleFunctions should be used as a data layer, workflow layer, agent layer, or execution-adjacent infrastructure.

​
What we need to start

The first conversation should be specific:
  • the desk, pod, product, or agent workflow you want to evaluate
  • the market family, catalyst set, or customer problem worth testing
  • the preferred output surface: API, SDK, Agent SDK, Slack-style note, CSV, internal dashboard, webhook, or FDE-assisted build
  • whether the first pass should remain read-only or include dry-run actions
  • one owner who can tell whether the output is useful
No broad vendor evaluation is required to begin. The pilot starts by finding one real workflow where prediction-market state might matter.

​
Start a pilot

If you are evaluating prediction-market infrastructure for a desk, pod, platform, or agent workflow, send a short note with the workflow you want to test. patrick@simplefunctions.dev

Direct API access

Use SimpleFunctions market state inside existing products and internal tools.

World state

Agent-readable event-probability state, deltas, and focused world feeds.

Trade intents

The object between reasoning and venue execution.

Market making

QuoteEngine, paper mode, inventory skew, spread, and operating gates.