Developer tools

Top 7 Prediction Market APIs & SDKs (2026)

Compare PMXT, Polymarket CLOB API, Kalshi API, PolyRouter, PredictorSDK, Oddpool and Polymarket Data API v2 for execution, fees and wallet analytics.

Tools at a glance

7 listed tools
  1. PMXT
  2. Polymarket CLOB API
  3. Kalshi API
  4. PolyRouter
  5. PredictorSDK
  6. Oddpool
  7. Polymarket Data API v2

Venue APIs expose native order books and execution; data tools add cross-venue discovery, historical data, fee comparisons or wallet analytics, and some SDKs also support trading. For active on-chain traders, the choice is between direct Polymarket execution, direct Kalshi execution, or a shared data layer across venues. This comparison is based on each provider's official documentation and published features, checked in November 2026; we have not tested the tools hands-on.

Which one to pick

  • Need native Polymarket execution: Polymarket CLOB API, with public order-book access and authenticated order management.
  • Need direct Kalshi integration: Kalshi API, with REST, WebSocket and FIX interfaces for event contracts.
  • Need one SDK for several venues: PMXT, with shared interfaces and trading methods where supported.
  • Need read-only market discovery and fee comparisons: PredictorSDK, with normalized data from ten venues and on-demand quotes.
  • Need historical order books and cross-venue flow: Oddpool, covering Polymarket and Kalshi, subject to its subscription restrictions.
  • Need lightweight multi-venue data or Polymarket wallet analytics: PolyRouter provides beta market-data endpoints; Polymarket Data API v2 exposes positions, trades and activity.

Compare execution, market data and cost

ToolType or Best forExecution and data accessPrice
PMXTUnified SDK and multi-venue tradingHosted search, historical data and venue-supported order methods; local execution modeSDK $0; hosted free tier with 25,000 credits/month; paid tiers $29.99 and $99.99/month. Personal use only.
Polymarket CLOB APINative Polymarket tradingPublic books and prices; authenticated order placement and managementNo API subscription price listed; market-specific trading fees apply.
Kalshi APINative event-contract tradingREST, WebSocket and FIX; separate production and demo environmentsAPI subscription price not published; exchange fees vary by market.
PolyRouterMulti-venue market dataREST market discovery, price history and sports endpointsFree open beta; published limit of 100 requests/minute.
PredictorSDKNormalized discovery and live quotesRead-only REST API; TypeScript, Python and Go clientsFree: 1,000 requests/month; paid tiers provide higher allowances.
OddpoolHistorical data and market-flow researchREST, WebSocket, historical books, trade data and cross-venue searchFree tier listed; Pro $30/month and Premium $100/month. New subscriptions paused.
Polymarket Data API v2Wallet and portfolio analyticsPublic REST endpoints for positions, trades, activity, PnL and market informationNo API key required; API subscription price not published.

The tools

PMXT

Unified data and trading SDK

Type or Best forUnified SDK and multi-venue trading

PMXT brings supported prediction-market venues behind shared Python and TypeScript clients. Its hosted service provides searchable market discovery, cross-venue matching and trading methods where supported. Alternatively, the local installation runs pmxt-core and communicates with venues using your own credentials. Hosted writes currently support Polymarket but not Kalshi; they use PMXT's prefunded escrow contracts on Polygon, while other write-capable venues require local mode. The SDK is MIT-licensed, while hosted access starts with 25,000 monthly credits on its free tier. Paid subscriptions are published at $29.99 and $99.99 monthly, with personal-use restrictions. Read the architecture documentation.

Choose it when you want shared market and order interfaces without maintaining every venue integration independently.

Watch out for the hosted escrow trust model and venue-level functionality. PMXT's hosted-service terms prohibit automated access, although its hosted-trading docs list bots as a use case. Its pages conflict on automated smart order routing: the homepage says 'Coming soon,' while the product page lists it. See the hosted trading documentation and current pricing.

Polymarket CLOB API

Native Polymarket order book

Type or Best forNative Polymarket tradingPriceNo API subscription price listed; market-specific trading fees apply.

Polymarket's Central Limit Order Book interface provides outcome-level bids, asks, available sizes, timestamps and book information. Public endpoints support market-data retrieval, while authenticated clients can sign, submit and manage market and limit orders. The current unified SDK uses an asset identifier that can represent either a legacy CTF token ID or a Protocol V2 position ID. Applications should obtain this identifier from the market response instead of relying on older hard-coded values. API subscription pricing is not listed in the trading documentation, and certain markets have taker fees. Consult the order-book reference and order instructions.

Choose it when Polymarket is your execution venue and your strategy depends on native liquidity and order-state information.

Watch out for market-version-specific identifiers and the wallet-signing requirements. Trading costs also differ across markets; the official fee documentation identifies which categories carry charges.

Kalshi API

Exchange-native event contracts

Type or Best forNative event-contract tradingPriceAPI subscription price not published; exchange fees vary by market.

Kalshi's Predictions API provides direct access to event-contract markets through REST, WebSocket and FIX. Its documentation includes separate production and demo environments, API authentication, market data and account-level order updates. Demo credentials cannot be reused against production endpoints. The exchange also publishes a fee schedule that distinguishes immediately matched trades from resting orders and identifies products with different fee arrangements. Kalshi is a centralized exchange integration, not an on-chain wallet or smart-contract interface. See the API reference and environment configuration.

Choose it when you need native Kalshi market access, account updates and direct order management.

Watch out for exchange-specific authentication, connection management and changing contract fees. Check the current fee schedule rather than assuming one rate applies to every market.

PolyRouter

Multi-venue market data

Type or Best forMulti-venue market dataPriceFree open beta; published limit of 100 requests/minute.

PolyRouter provides a unified REST interface for market discovery, current prices and historical information. Its documentation lists Polymarket, Kalshi, Manifold Markets, Limitless, ProphetX, Novig and SX.bet. Sports-specific endpoints provide another route for applications tracking games and related contracts. PolyRouter is free and in open beta, with a limit of 100 requests per minute. Requests use an API key in the X-API-Key header. The documented interface provides market data, not order execution. Read the platform documentation and API reference.

Choose it when you need a straightforward multi-venue feed for research or a market-monitoring application.

Watch out for beta-stage changes. Validate market identifiers and source timestamps before using aggregated quotes in a live strategy.

PredictorSDK

Normalized discovery and live quotes

Type or Best forNormalized discovery and live quotesPriceFree: 1,000 requests/month; paid tiers provide higher allowances.

PredictorSDK offers a unified catalog covering ten prediction-market venues, with generated TypeScript, Python and Go clients. Its market-matching endpoints connect equivalent sports listings, while individual market-detail requests retrieve current prices, bids, asks and published fee information from the underlying venue. The free allowance is 1,000 requests per UTC month, with a documented rate limit of ten requests per minute. Paid plans increase request capacity and throughput. Its fee model also distinguishes missing information from an explicitly fee-free market, The official documentation describes its API and supported venues.

Choose it when you want a consistent discovery and pricing layer while keeping order execution under direct venue control.

Watch out for its read-only design and the fact that market matching does not guarantee identical contract terms. Check request allowances and the fee calculation guide before deploying a high-volume scanner.

Oddpool

Historical books and cross-venue feeds

Type or Best forHistorical data and market-flow research

Oddpool provides normalized prediction-market information from Kalshi and Polymarket. Its API includes market search, historical OHLCV, top-of-book records, full-depth order-book history, trade tapes, whale activity and WebSocket streams. The published free allowance is 1,000 requests per month at one request per second; the listed Pro and Premium subscriptions cost $30 and $100 monthly. There is an important access restriction: its pricing page states that new subscriptions are no longer accepted, while existing free accounts continue operating. See the API documentation and the pricing and availability page.

Choose it when you already have access and need historical liquidity, trade-flow information or normalized streams from its supported venues.

Watch out for restricted onboarding and plan-dependent endpoint access. The free allowance does not include every WebSocket channel or premium research endpoint; check the published limits.

Polymarket Data API v2

Wallet and activity analytics

Type or Best forWallet and portfolio analyticsPriceNo API key required; API subscription price not published.

Polymarket Data API v2 is the venue's public analytics interface for positions, trades, activity, portfolio value, user PnL, market state and leaderboards. Its endpoints require no API key or authentication token, making it useful for wallet-monitoring applications and historical research. It complements rather than replaces the CLOB: use the latter for live order books and trading operations. The v2 specification uses opaque cursors for pagination, while individual endpoints define their own history windows. Missing numeric fields represent unavailable data, not zero. The official v2 API reference documents the response formats and pagination behavior.

Choose it when you need to monitor Polymarket wallet activity, holdings and performance without managing trading credentials.

Watch out for its single-venue scope and endpoint-specific historical coverage. It cannot submit or manage orders, and downstream analytics must preserve null values and follow the documented cursors.

How to compare executable prices across prediction markets

  1. Define the exact contract. Record the proposition, outcome, expiry, settlement source, cancellation conditions and timezone. A shared event headline is not sufficient: two crypto-price contracts can use different indexes or observation windows and therefore represent different bets.
  2. Discover the available listings. Search the PredictorSDK catalog or PMXT Router for candidate markets. PolyRouter provides another discovery route, while Oddpool can supply historical context. Save the native market identifier and the venue associated with each result.
  3. Retrieve actual order books. Request Polymarket's CLOB book and obtain Kalshi data through its REST or WebSocket interface. Record bid, ask, size, timestamp and book hash where available. Aggregated prices and historical snapshots are useful context, but they should not replace a current execution quote.
  4. Normalize the contract and units. Confirm the same outcome and settlement conditions, then convert prices into a consistent probability representation. Account for differences between shares and contracts, collateral denominations and contract multipliers. Use PredictorSDK's published fee fields where available, then verify the actual venue schedule.
  5. Calculate the cost for your intended size. Walk the available order-book levels rather than multiplying the first displayed ask by your position size. Calculate the volume-weighted entry price, include applicable maker or taker fees, and account for relevant funding, conversion and network expenses.
  6. Execute through the appropriate venue. Submit a limit order using Polymarket CLOB or Kalshi's native API, or use a PMXT order method only when its documentation confirms support for the specific venue. Test through Kalshi's demo environment where applicable. Keep signing credentials server-side and enforce an order-size ceiling.
  7. Reconcile the result. Track acknowledgements, partial fills, cancellations and final positions. For Polymarket, retrieve positions, trades and activity through Data API v2 using its cursor pagination. Compare those records with execution updates and your internal ledger.

Worked example (illustrative): Suppose two venues list apparently equivalent YES contracts. Venue A offers 100 shares at $0.60, while Venue B offers 20 at $0.59 and the next 80 at $0.62. Buying 100 shares costs $60.00 at A but $61.40 at B before fees, despite B displaying the lower initial ask. Add each venue's actual trading charges before deciding where the order belongs.

Contract, liquidity and execution risks

Market-matching software can group similar headlines whose resolution sources, cutoffs, void conditions or settlement windows differ; verify the underlying contract before treating two positions as a hedge. Automated strategies should reject stale books, enforce price-deviation and exposure limits, handle partial fills and disconnected streams, and reconcile every completed order against the venue's account records.

Frequently asked questions

Can one API place trades across every prediction market?

No universal execution interface guarantees identical trading functionality everywhere. PMXT provides supported order methods across multiple venues, but authentication, order types and execution capabilities remain venue-dependent.

Does a 60-cent ask mean I can buy at 60 cents?

Only for the quantity available at that price. Larger orders can consume several price levels, so the average fill may be materially different from the initial quote.

Which Polymarket API should I use for wallet tracking?

Use Data API v2 for public positions, trade history, activity and PnL information. The CLOB interface serves a different purpose: order-book access and trading operations.

Can I compare the same event on Kalshi and Polymarket?

Yes, provided the contracts have equivalent outcomes, settlement sources, expiry conditions and resolution rules. A matching title or similar probability does not establish contractual equivalence.

How do I keep prediction-market quotes current?

Use venue WebSocket subscriptions for ongoing updates and REST snapshots to initialize or rebuild book state. On reconnect, resynchronize rather than assuming that previously cached levels remain valid.

Are API charges the same as prediction-market trading fees?

No. An API subscription pays for data access or request capacity, while trading charges arise from venue execution rules. Calculate both separately when estimating the total operating cost of a trading system.

Sources

Show all 19 sources