The loop
1
Ask for an event
Start with a natural-language question or a ticker. The query layer maps it to Kalshi, Polymarket, source context, related markets, and follow-up actions.
2
Normalize the market
Venue-specific contracts become stable objects with identifiers, prices, liquidity, status, history, regime state, and links back to the source.
3
Attach context
Government, economic, traditional-market, and topic-level evidence stay in separate fields. Agents do not need to reverse-engineer prose.
4
Watch changes
World-state and delta endpoints let an agent wake on market movement, source changes, or monitored thesis conditions instead of running broad search loops.
5
Act through workflows
Responses point to inspect, screen, monitor, portfolio, and execution-intent surfaces. SimpleFunctions exposes software workflow state; it is not a broker, exchange, custodian, FCM, or investment adviser.
Core objects
Why this is different from a venue API
Venue APIs expose markets. SimpleFunctions returns event probability state:- cross-venue contracts
- source context
- world-state snapshots and deltas
- market screens and inspection links
- user-scoped portfolio state when authenticated
- next actions for agents and operator workflows