Automated markets
A data feed proposes the event, the platform opens the market, and the same feed brings the result back. Where the outcome is a judgement call a person confirms it; where it is a published number, it settles itself.
SportsLive in demo
Football fixtures
football-data.org · Premier League on the demo
- Each upcoming fixture becomes one market: will the home team win in regulation time? A draw resolves NO.
- Markets open up to two weeks ahead and close at kick-off, so nobody trades a match already being played.
- An AI model only words the fixture it is given. It cannot add teams, dates or facts, and output that disagrees with the feed is rejected.
- After the match the system proposes the result with a link to the source. An admin confirms or overrides it — fixtures can be abandoned, awarded or replayed, so a person decides.
- Postponed or cancelled fixtures are flagged to the admin, never settled silently.
- Other competitions are a configuration change. The data provider is one adapter, so you can bring your own.
CryptoLive in demo
Hourly up or down
Binance public market data · BTC, ETH, SOL on the demo
- One market per coin per hour on the UTC clock: will it close at or above the price it opened the hour at?
- Listed before the hour starts, so nobody can buy an answer that is already known. Trading stays open through the hour.
- The opening and closing prices come from a single published Binance 1-hour candle. A tie resolves YES.
- Settles on its own, with no admin needed — there is no judgement to make. The candle's URL is stored on the market so anyone can re-check the result.
- The house's worst-case loss on each market is fixed in advance by its liquidity subsidy.
- Coins are a configuration list; hourly runs on the demo, and the cycle length is configurable.
For every feed
Review queue
Generated markets can land as drafts for an admin to publish, or go live automatically — set per subject, so a feed earns trust before it runs unattended.
Labelled at source
Every generated market shows which feed created it and from which record, so traders can see where a question came from.
Never duplicated
Each market is tied to the feed's own event id. A re-run, a restart or a double-fire creates nothing new.
Job health on screen
Admins see every background job's last run, duration, outcome and last error. A failing feed is visible without reading server logs.
Fails closed
A missing key, a rate limit or a response in an unexpected shape creates no markets and shows an error. No feed record, no market.
House account, not an admin
Automated markets are opened by a dedicated non-admin house account, with a balance floor that warns before its wallet runs dry.
Adding a subject — another sport, elections, macro data — means one feed adapter and one configuration entry. Nothing else in the platform changes.