Kairos vs Prediction Hunt

What Kairos does

Cross-venue trading terminal that merges Kalshi, Polymarket and Predict.fun into one order book. Matching contracts on different exchanges are shown as a single instrument with a composite ladder and a global best bid and offer, so you can see which venue is actually cheapest before you send, and an order to the NBBO endpoint routes to whichever book shows that price. Feeds are ingested next to the venues and merged in the browser with no polling interval; the ticket carries GTC, GTD, FOK, FAK and IOC time-in-force, post-only and slippage caps, with batch cancel and a per-venue kill switch. A bots panel runs parameterised templates — market making, cross-venue arbitrage, dip buying — against recorded books first and promotes the same config to live. The same engine is exposed as a REST and WebSocket API with scoped keys, IP whitelisting and a free read-only market-data tier. Built by a team from high-frequency trading firms and exchanges and backed by a $2.5M seed led by a16z.

• Composite order book and NBBO across three venues, with prices, probabilities and share counts normalised to one convention
• Sub-second colocated feeds merged client-side over WebSocket — quotes and fills land without polling
• Pro order ticket: GTC / GTD / FOK / FAK / IOC, post-only, slippage caps, batch cancel of up to 100 orders and a per-venue cancel-all kill switch
• Bot templates for market making, cross-venue arbitrage and dip buying, backtested on recorded books and promoted to live unchanged
• Draggable workspace with saved layouts, positions, orders, time and sales, holders and market rules on one screen

• Aggregation is the product: the same event often trades at different prices on Kalshi, Polymarket and Predict.fun, and a single-venue app cannot see the gap. Kairos builds one book across all of them so the cheapest side is visible and routable from one ticket.
• Execution is self-custodial through Turnkey enclaves — Kairos signs within a policy you set, or hands you an EIP-712 payload to sign yourself on allow-listed accounts — and keys are exportable. That is still signing authority held by a third party, which is why the custody line above does not say non-custodial.
• The bots are templates, not a track record: nothing on the site publishes live P&L for any strategy, and the terminal itself sits behind an account we did not create. What we exercised is the public surface — docs dated Aug 21, 2026, the data dashboard reading both venues' APIs, and the API endpoints answering as documented.