← Developer tools

Find your toolkit

Polymarket SDKs and developer libraries | Page 2

A client library helps your code work with a documented interface. Select it for the data, account operation or research task you need, rather than assuming every Polymarket SDK covers the same services.

How to choose sdks & libraries

Map library coverage to your application

Check the methods you intend to call and the API behind each one. A library for one service or action may not cover market discovery, historical data and trading together. Compare language support with your application’s runtime and deployment requirements.

Review before adopting

  • Confirm the programming language and supported deployment environment.
  • Check the exact API methods and data or account operations the library documents.
  • Identify any hosted service, API entitlement or credential required in addition to installing the package.

Downloading a library supplies code, not automatic access to a hosted dataset or permission to trade. Keep API access and signing permissions separate from package installation. Choose a CLI for command-line work or an MCP server when the intended caller is an assistant.

25 tools · 13–24 shown

Narrow your search

Find the right tools

polymarket-api-python quickstart and public book reads
SDK3.5Editorial

Read markets and liquidity metrics in Python, maintain CLOB streams and add trading only when needed.

  • Language Python
Polynode Charts SDK example and real-time data displays.
Data API3.5Editorial

Filtered WebSockets, wallet history, market metadata and order-book data with explicit account-level limits.

  • Access API · CLI
PolyOrderbooks historical L2 overview and provider book example
Dataset3.5Editorial

Query historical books at 250 ms intervals or replay supported crypto strategies with depth-based fills.

  • Access Web · API · MCP
prediction-market-backtesting framework and release capabilities
SDK3.5Editorial

Replay historical Polymarket data in NautilusTrader, compare parameters and inspect portfolio and execution reports.

  • Language Python · Rust
River Markets presentation of multi-venue API access
Trading terminal3.5Editorial

A professional terminal and signed API for multi-venue orders, fills, positions and strategy PnL.

  • Access Web · API
Simmer SDK introduction and integration paths
SDK3.5Editorial

Develop agent strategies with research, paper trading, replay and supported live integrations.

  • Language Python
  • Access CLI
Telonex page describing historical Polymarket data for research and backtesting
Dataset3.5Editorial

Daily Parquet market history with event-level books, on-chain fills and separate licensing for commercial use.

  • Access API
UnifAI top-performer presentation
Platform3.5Editorial

A DeFi agent platform with reusable strategies, a continuous execution layer and documented Polymarket endgame workflows.

  • Access Web
OrderbookTrade explanation of its execution and platform workflow
OrderbookTraderestricted
Infrastructure3.0Editorial

Integrate order actions, matching and market-making tools through shared API and WebSocket infrastructure.

  • Access API
Poly SDK features, installation and services
SDK3.0Editorial

Combine data clients, wallet tracking and strategy examples in a third-party TypeScript toolkit.

  • Language TypeScript
Predictefy product overview
Data API3.0Editorial

Normalized prediction-market data, matched contracts, replay and paper trading for multi-venue research.

  • Access Web · API · MCP
Polymarket Agents repository framework and modular research features
SDK2.5Editorial

Connect market data, retrieved research and model prompts in an official Python framework that needs development work.

  • Language Python
  • Access CLI