Infrastructure
Bot infrastructure for prediction markets
Libraries and frameworks that handle venue plumbing so a bot can trade Kalshi and Polymarket through one interface.
Checked September 8, 2026 · every price read off the live site
Every infrastructure bot
2 reviewed · alphabetical-
Kairos Cross-venue trading terminal: Kalshi, Polymarket and Predict.fun in one order book, with sub-second data and advanced order types.
-
03PMXT Not a strategy, the plumbing: CCXT-style unified library across 15+ venues. Several of the better arb bots are built on it.
-
polymarket-tennis The data layer for a Polymarket tennis bot: market discovery, match identity resolution and a joined price-versus-score view.
| Bot | Venues | Pricing | Type |
|---|---|---|---|
| PMXT | Polymarket, Polymarket US, Kalshi, Limitless, Probable, Baozi, Myriad, Opinion, Metaculus, Smarkets, Hyperliquid, Gemini Titan, SuiBets, Rain, Hunch | Open source (MIT). | library |
| polymarket-tennis | Polymarket | Open source (MIT). | library |
How these bots work
Infrastructure entries are not strategies. They are the libraries a bot is written on: unified venue clients, market discovery, identity resolution between a market and the real-world event it prices. Several arbitrage bots in this directory import PMXT rather than talking to Polymarket and Kalshi directly.
The trade-off is coverage against fidelity. A unified client lets one bot run on many venues, but each venue's quirks (Kalshi's RSA-PSS signing, Polymarket's EIP-712 orders and proxy wallets, per-venue order types) get flattened, and the library's compliance table becomes the thing you audit.
Two entries here: PMXT for cross-venue trading and data, and polymarket-tennis for a single sport's market discovery and live-score join.
How to choose
- Check the per-venue feature table for the exact venue and order type you need before assuming the abstraction covers it.
- Decide hosted versus self-hosted: hosted keys mean someone else signs and settles; self-host means your credentials stay local.
- Count runtime dependencies. PMXT's Python SDK needs Node.js installed; polymarket-tennis needs only httpx.
- Look at how ambiguity is handled. A matcher that returns nothing on doubt beats one that guesses and pairs the wrong markets.
- Confirm the maintainers' incentive. Vendor-authored tooling is fine when the README says so and the paid tier is optional.
Questions about infrastructure bots
What is the CCXT of prediction markets?
PMXT describes itself that way: a unified API across 15 venues with Python and TypeScript SDKs, MIT licensed, with a hosted option.
Do I need PMXT to build a Polymarket bot?
No. Polymarket's own SDKs work. PMXT helps when the same bot must run on more than one venue.
Is there a free data library for Polymarket sports markets?
polymarket-tennis covers tennis on Polymarket's keyless Gamma API and joins it to live scores on a free-tier API, observe-only.
Bots die in execution. Terminals are execution.
Wanted a bot for speed and cross-venue vision? The free Kairos terminal trades Kalshi, Polymarket and Predict.fun from one book, no keys to manage.