Name: Poly SDK: editorial review
Rating: 3
Author: PredictionToolkit

What is Poly SDK?

The repository goes beyond raw data requests: smart-money subscriptions, copy sizing, CTF actions and short-duration crypto strategy examples connect research to possible execution. Configuration and ongoing operation belong to the application using the code.

Review the package version and dependencies before adapting examples. Some subgraph and RTDS surfaces are legacy, and token-array shapes changed between versions. Compatibility and execution controls therefore need to be checked for the specific version used.

Who it is for

TypeScript developers prototyping wallet following.
Builders seeking service-level helpers beyond raw requests.
Studying copying and two-leg state machines.

Features and coverage

Data clients
Use Gamma discovery, account data and wallet research methods.
Wallet subscriptions
Filter selected wallet activity by address and size.
Copy rules
Set scale, maximum trade size, slippage, side filters and dry-run behavior.
Arbitrage service
Scan books, size legs and manage configured execution and rebalancing.
Dip examples
Study a two-leg state machine for short-duration crypto markets.
CTF actions
Examples cover split, merge and redemption.
Typed workflows
Explore order, rewards, candle and WebSocket examples.

Workflows with Poly SDK

Prototype copying

Choose addresses, set scale and a maximum, and use dryRun. Inspect detected and skipped activity before signed execution.

Trace a two-leg strategy

Follow the first fill, pending second leg and cleanup separately. The first fill creates exposure before a matching leg is available.

Pricing and total cost

The source is MIT-licensed. Runtime, dependent providers, venue fees and capital costs remain separate.

Getting started

Before you start: A two-leg strategy can remain exposed after only its first fill.

Read the repository’s current package instructions.
Begin with a public-data example.
Select a service and set size and execution controls explicitly.
Use dry-run behavior where documented.
Check contracts, feeds and version migration notes before live integration.

Legacy dependency, subgraph and RTDS examples need compatibility review against current Polymarket documentation.

Read copying documentation

Useful links

What to check

A two-leg strategy can remain exposed after only its first fill.
autoExecute and dryRun affect whether services submit orders.
Token-array changes require version-specific migration handling.
Legacy examples do not establish current provider compatibility.

A closer look

Ratings & reviews

Editorial rating

3.0/ 5

0 user reviews

PredictionToolkit editorial

Our take on Poly SDK

Wallet clients and strategy examples are useful for prototyping. Legacy integrations and execution-capable services require compatibility work and careful configuration.

Based on documented features, setup and access terms. How we rate

User reviews 0

The main score switches to user ratings after 5 published reviews.

Be the first to share your experience

A specific example helps the next person choose the right tool.

Related tools

Browse category

Frequently asked questions about Poly SDK

Is it the official Polymarket SDK?

No. It is a third-party toolkit with additional services.

Can I inspect copying without orders?

The copy service documents a dryRun setting.

Does an arbitrage signal complete the trade?

No. Detection, execution, partial fills and cleanup are separate states.

Poly SDK: prototype Polymarket services with explicit execution controls

Screenshots and interface