Table of Contents
Last updated: 14 October 2026 | Reviewed by Mathibharathi Mariselvan, Co-founder, Pixel Web Solutions | 14 min read
A Polymarket trading bot is a program that reads Polymarket's order book through its CLOB API and places signed orders automatically, usually to make markets, arbitrage price gaps against venues like Kalshi, or react to news faster than a human. In 2026 it must use Polymarket's CLOB V2 and unified SDKs, account for taker fees of up to 1.75 cents per share, and respect a geoblock that puts the US, UK, Singapore and Brazil in close-only mode on the international platform. US traders can still automate legally through Polymarket US, the CFTC-regulated exchange, which offers its own API after identity checks.
Most Polymarket bot guides and GitHub repos were written for the old stack. Since 28 April 2026, Polymarket's changelog says legacy V1 SDKs and V1-signed orders no longer work on production, so a bot copied from a 2024 tutorial simply fails to trade. Fees changed too: most categories now charge takers.
This guide is built from Polymarket's own developer documentation, Polymarket US and Kalshi fee schedules, and a worked arbitrage trade with every fee counted. It covers what the API actually offers, which strategies hold up, the risk limits that keep a bot alive, where you can legally run one, and what a build costs.
Key Takeaways
- The stack moved. CLOB V2 went live on 28 April 2026; V1 SDKs stopped working, collateral is now pUSD on Polygon, and the official Python package is
polymarket-client. - Fees decide strategy. Takers pay
C x feeRate x p x (1 - p), from 0.04 to 0.07 by category, while makers pay nothing, so most durable bots quote as makers. - Arbitrage is thinner than it looks. At mid-range prices, two taker legs on Polymarket US and Kalshi cost about 3.5 cents per contract, so a 3-cent gap loses money.
- Access depends on where you are. The US, UK, Singapore and Brazil are close-only on Polymarket's international API; US residents can trade through Polymarket US with KYC and API keys.
- Risk limits are mandatory. Per-market caps, a stale-data kill switch, price guards and rate-limit headroom matter more than the signal.
- Build cost starts at $6,000. Pixel Web Solutions prices a single-strategy trading bot from $6,000; multi-venue arbitrage systems are larger custom builds.
What a Polymarket Trading Bot Actually Does
Polymarket runs a central limit order book (CLOB) for binary outcome shares that pay $1 if the outcome happens and $0 if not. Orders are signed off-chain and matched by Polymarket's operator, then settled on Polygon. Polymarket's trading overview states that the operator can match and order trades but cannot set prices or execute trades users did not sign.
A bot automates four jobs: read the book and price feeds, decide a fair value and an action, sign and send orders within the market's tick size and minimum size, and manage fills, inventory and cancellations. Everything else, from AI forecasting to Telegram alerts, sits on top of that loop.
The order types you get
Polymarket's market making guide lists four order types:
| Order type | Behaviour | Typical bot use |
|---|---|---|
| Good-Til-Cancelled (GTC) | Rests until filled or cancelled | Passive two-sided quotes |
| Good-Til-Date (GTD) | Rests until filled, cancelled or expired | Quotes that must vanish before a known catalyst |
| Fill-or-Kill (FOK) | Fills the full size immediately or cancels | Arbitrage legs where a partial fill is useless |
| Fill-and-Kill (FAK) | Fills what it can, cancels the rest | Fast rebalancing that accepts partial fills |
A post-only flag on GTC or GTD orders rejects the order if it would take liquidity, which guarantees maker pricing. Orders cannot be edited in place, so a quote update is always a cancel plus a new order.
The 2026 Polymarket API Stack
The building blocks changed more in 2026 than in the previous three years combined.
| Component | What it is in October 2026 | Why your bot cares |
|---|---|---|
| CLOB V2 | Order book at clob.polymarket.com, V2 signing only since 28 April 2026 |
Old V1 bots and open orders did not migrate |
| pUSD | ERC-20 on Polygon backed by USDC, the collateral for all trading | Bots must hold and approve pUSD to trade |
| Unified SDKs | polymarket-client for Python, plus a TypeScript SDK |
Replaces py-clob-client for new builds |
| Market and user WebSockets | Real-time book and order updates | Never poll the book in a live strategy |
| PolyBolt WebSocket | Crypto, equity and Chainlink TWAP reference prices, launched 15 September 2026 | Reference prices for crypto up or down markets |
| Data API v2 | Trades, positions, PnL and price history, live 4 September 2026 | Backtesting and reconciliation |
| Per-signer rate limits | Token buckets by 30-day volume tier | Caps how fast you can quote and cancel |
Polymarket's pUSD page describes it as a 6-decimal token whose USDC backing is enforced on-chain. The Python SDK page names polymarket-client as the official package.
Rate limits by volume tier
Polymarket's trading rate limits give every signer separate order and cancel buckets. A Standard account refills 40 order tokens and 80 cancel tokens per second, with bursts of 60 and 120. Higher 30-day volume raises that: Silver ($100,000+) reaches 200 orders per second and Platinum ($2.5 million+) 450. A batch that exceeds the bucket is rejected whole, so a bot that sends large batches must size them below its burst capacity.
What the GitHub repos tell you
Search GitHub for a Polymarket bot and the top results are often stale. As of 16 October 2026, Polymarket's own agents repository has about 3,800 stars but its last push was in November 2024, before CLOB V2. The legacy py-clob-client has about 1,200 stars, while the newer py-clob-client-v2 was updated on 15 October 2026. Read the commit date before you read the README.
Polymarket Bot Strategies That Survive Fees
Not every strategy that works in a backtest survives fees, latency and resolution risk. Here are the four that real bots run, with the honest downside of each.
1. Market making
The bot posts bids and asks around its fair value and earns the spread. Makers pay no Polymarket fee and can earn liquidity rewards and maker rebates on fee-enabled markets. In binary markets, buying NO at 0.48 is economically the same as selling YES at 0.52, so the bot can quote either side.
The risk is adverse selection. When news breaks, informed traders hit stale quotes first. Polymarket's own guidance is to skew quotes on inventory, cancel stale quotes immediately, and use GTD orders that expire before known catalysts.
2. Cross-venue arbitrage with Kalshi
When the same event trades on two venues, buying YES on one and NO on the other for less than $1 locks in the difference at resolution. For US traders the legal pairing is Polymarket US with Kalshi, both regulated by the CFTC.
The risks are rule mismatch and leg risk. Two venues can word the same question differently, use different resolution sources, or settle on different dates. One leg can fill while the other moves away. Capital also sits locked until both markets settle.
3. News and resolution timing
Bots that parse official data releases, scores or announcements can trade seconds before humans react. Near the end of a market, some bots buy outcomes trading at 97 to 99 cents once the result is public but not yet resolved. Polymarket's resolution process uses the UMA Optimistic Oracle with a two-hour challenge period and a typical $750 bond, so a disputed market can take days.
The risks are disputes and rules. A 98-cent position can resolve to zero if the rules read differently from the headline. On Polymarket US, the trading restrictions bar trading on confidential information or by people who can influence the outcome. For crypto up or down markets, Polymarket's changelog shows a 150 millisecond taker delay on crypto markets since 4 September 2026, which blunts pure speed plays.
4. Complete-set and multi-outcome pricing
In multi-outcome events, Polymarket uses negative-risk markets, where the YES prices across all outcomes should sum to about $1. A bot can watch for sums that drift below or above that and trade the gap. The risk is execution: gaps close fast, and buying five legs as taker pays five fees.
| Strategy | Edge source | Fee profile | Main risk | Suited to |
|---|---|---|---|---|
| Market making | Spread plus rewards | Maker, no fee | Adverse selection on news | Steady capital, good infrastructure |
| Cross-venue arbitrage | Price gap between venues | Often one taker leg | Rule mismatch, leg risk | US traders with both accounts |
| News and resolution timing | Speed and rule reading | Taker | Disputes, insider rules | Strong data feeds |
| Multi-outcome pricing | Sum of prices off $1 | Several taker legs | Gaps close before fills | Low-latency builds |
Worked Example: A Polymarket US and Kalshi Arbitrage, With Fees
Take a hypothetical event listed on both CFTC-regulated venues, with identical resolution rules. Polymarket US offers YES at $0.55, and Kalshi offers NO at $0.42. Buying 1,000 of each costs $970 and pays $1,000 whatever happens, a gross edge of $30 (3.09 percent).
Now add fees. Polymarket US charges takers 0.0695 x C x p x (1 - p) according to its fee schedule. Kalshi's fee schedule charges takers 0.07 x C x P x (1 - P), rounded up to the cent.
Case A: both legs as taker
- Polymarket US fee: 0.0695 x 1,000 x 0.55 x 0.45 = $17.20
- Kalshi fee: 0.07 x 1,000 x 0.42 x 0.58 = $17.052, rounded up to $17.06
- Total outlay: $550 + $420 + $17.20 + $17.06 = $1,004.26
- Result: $1,000 payout minus $1,004.26 = a loss of $4.26
Case B: Polymarket US leg as a filled post-only maker order
- Polymarket US fee: $0 (makers pay no taker fee)
- Kalshi fee: $17.06
- Total outlay: $550 + $420 + $17.06 = $987.06
- Result: $1,000 minus $987.06 = a profit of $12.94, or 1.31 percent
- If both markets settle in 45 days: 1.31% x 365 / 45 = about 10.6 percent annualised, before funding costs
| Case A: taker and taker | Case B: maker and taker | |
|---|---|---|
| Gross edge | $30.00 | $30.00 |
| Polymarket US fee | $17.20 | $0.00 |
| Kalshi fee | $17.06 | $17.06 |
| Net result | minus $4.26 | plus $12.94 |
The rule of thumb: near 50 cents, two taker legs cost about 0.0695 x 0.25 + 0.07 x 0.25, or roughly 3.5 cents per contract. A cross-venue gap smaller than that is a loss unless one leg rests as a maker, and a resting leg brings back leg risk. That trade-off is the whole design problem of an arbitrage bot.
Risk Limits Every Polymarket Bot Needs
A bot fails from its worst minute, not its average day. These limits are starting points to tune, not universal settings:
- Position cap per market: a fixed share of bankroll, for example 2 to 5 percent, so one bad resolution cannot end the strategy.
- Event cap: a ceiling across all correlated markets on the same event or date.
- Daily loss limit: stop quoting and cancel all orders when realised plus unrealised loss crosses it.
- Stale-data kill switch: if the market WebSocket goes quiet for a few seconds, call cancel-all. Polymarket's guide names a kill switch as a core control.
- Price guard: reject any order more than a set distance from the book midpoint.
- Catalyst expiry: use GTD orders that expire before scheduled news, debates or data releases.
- Rate-limit headroom: run below about half of your tier's burst capacity so cancels still pass in a fast market.
- Rules check: store each market's resolution source and end date, and block trades where two venues' rules differ.
Where You Can Legally Run a Polymarket Bot
Polymarket publishes its blocked countries on its geographic restrictions page, with a GET https://polymarket.com/api/geoblock endpoint that returns whether the calling IP is blocked. Using a VPN to get around it breaks Polymarket's rules and can get funds frozen.
| Jurisdiction | Polymarket international | Legal route to automate |
|---|---|---|
| United States | Close-only on frontend and API | Polymarket US (CFTC DCM) API after KYC, or Kalshi |
| United Kingdom | Close-only on frontend and API | No Polymarket route; check UK gambling and FCA rules first |
| Singapore | Close-only on frontend and API | No Polymarket route; check local law |
| Brazil | Close-only on frontend and API | No Polymarket route; check local law |
| France, Germany, Italy, Poland, Belgium, Australia, Taiwan, Thailand | Close-only on frontend and API | No Polymarket route |
| Iran, Syria, Cuba, North Korea, occupied Ukrainian regions | Fully blocked (OFAC) | None |
| Ireland, Japan, Netherlands, South Korea | Close-only on the website; API not restricted | Take local legal advice before automating |
Polymarket US is a fiat-based exchange operating as a designated contract market and derivatives clearing organisation under CFTC oversight, trading in US dollars. Its API quickstart issues a key ID and secret through a developer portal once identity verification is approved, with a polymarket-us SDK for TypeScript and Python. Polymarket US is a separate venue with its own markets and liquidity, not a door into the international book.
For a market-by-market view of how regulators treat event contracts, see Pixel's guide to prediction market regulations and compliance.
Python, GitHub and Telegram: Building the Bot
A production bot has five parts, whatever the strategy:
- Market data: WebSocket book and trade streams, PolyBolt reference prices, and Data API v2 history for backtests.
- Strategy engine: fair value, quoting or signal logic, written in Python for research speed or TypeScript or Rust where latency matters.
- Order manager: V2 signing, tick and minimum-size validation, batching under the rate-limit bucket, and reconciliation after reconnects.
- Risk engine: the limits above, enforced before every order and on a timer.
- Control plane: dashboards and alerts. Many teams use a private Telegram bot for fill alerts, PnL and a remote pause command.
A warning on third-party Telegram bots: a Polymarket copy-trading or sniper bot run by someone else usually asks for your private key or a session key. Polymarket's session keys can scope and time-limit what a signer may do, so a well-built bot asks for a scoped key, never your main wallet. Polymarket also notes that its primary servers run in eu-west-2, and that market makers who complete KYC can apply to co-locate there.
For the general build process behind any trading bot, from backtesting to deployment, Pixel's guide on how to build a crypto trading bot walks through each stage.
How Much Does a Polymarket Trading Bot Cost?
A Polymarket trading bot costs from $6,000 for a single-strategy build with Pixel Web Solutions. Larger systems are custom, so the ranges below are engineering estimates at Pixel's custom rate from $40 per hour, with the hours shown.
| Scope | What it includes | Estimated hours | Cost |
|---|---|---|---|
| Single-strategy bot | One venue, one strategy, risk limits, basic dashboard | n/a | From $6,000 (Pixel published price) |
| Market-making bot | Inventory skew, GTD catalyst expiry, rewards tracking, kill switch | 250 to 400 | $10,000 to $16,000 (estimate) |
| Cross-venue arbitrage | Polymarket US and Kalshi connectors, market mapping, rules check, leg-risk handling | 350 to 600 | $14,000 to $24,000 (estimate) |
| Backtesting and paper trading | Data API v2 history, fee-aware simulator | 80 to 150 | $3,200 to $6,000 (estimate) |
| Telegram control plane | Alerts, PnL reports, pause and resume commands | 30 to 60 | $1,200 to $2,400 (estimate) |
Running costs are small next to trading capital: a cloud server near the venue, data feeds, and monitoring. The real cost is the capital the strategy needs and the fees it pays, which the worked example above shows can erase a thin edge.
Bot or platform?
A trading bot uses someone else's market. If the goal is to run the market yourself and earn the fees, that is a different build: Pixel's Polymarket clone script covers prediction market platforms from $7,000. To see which venues have the volume worth trading, compare the top prediction market platforms.
Should You Build a Polymarket Bot? A Quick Checklist
- Are you legally allowed to trade on the venue you plan to automate, from where you live?
- Does your edge beat the fee curve at the prices you trade, after the 3.5-cent two-taker rule?
- Can your bot quote as a maker for at least one leg, and survive news without stale quotes?
- Do you store resolution rules and refuse trades when venues disagree?
- Is your code on CLOB V2 and pUSD, not a 2024 repository?
- Have you paper-traded for long enough to see a disputed resolution and a fast market?
If you cannot answer yes to the first two, a bot will only lose money faster.
How Pixel Web Solutions Can Help
Pixel Web Solutions builds trading bots for prediction markets and crypto venues, including market makers, cross-venue arbitrage engines and Telegram control planes, on the current Polymarket CLOB V2 and Polymarket US APIs. Its crypto trading bot development service starts from $6,000 for a single-strategy bot, with risk limits, fee-aware backtesting and geoblock checks built in rather than bolted on. Pixel builds the software; traders remain responsible for their own legal eligibility and capital. To scope a bot, contact Pixel Web Solutions.
Frequently Asked Questions
Is it legal to use a Polymarket trading bot?
Automated trading through Polymarket's API is allowed where Polymarket itself is allowed. The international platform puts the US, UK, Singapore, Brazil and others in close-only mode, so new orders from those places are rejected. US residents can automate on Polymarket US, the CFTC-regulated exchange, after identity checks.
Can I run a Polymarket bot in Python?
Yes. Polymarket's official Python SDK is polymarket-client, which supports the CLOB V2 order signing required since 28 April 2026. Older repositories built on the original py-clob-client need migrating before they can trade.
Are Polymarket bots profitable?
Some are, mostly market makers and well-capitalised arbitrage systems, but profit is not guaranteed. Taker fees of up to 1.75 cents per share at 50 cents, adverse selection on news and resolution disputes remove most simple edges. Paper-trade first.
What fees does a Polymarket bot pay?
Makers pay nothing. Takers pay C x feeRate x p x (1 - p), with fee rates of 0.07 for crypto, 0.05 for sports and several other categories, 0.04 for politics, finance, tech and mentions, and zero for geopolitics, according to Polymarket's fees page.
Can a bot arbitrage Polymarket and Kalshi?
Yes, if the trader is eligible on both venues and the two markets resolve on identical rules. At mid-range prices, two taker legs cost about 3.5 cents per contract, so profitable trades usually need one maker leg or a wider gap.
Is there an official Polymarket bot on GitHub?
Polymarket publishes an open-source agents framework and official SDKs on GitHub. The agents repository was last updated in November 2024, before CLOB V2, so treat it as a reference design rather than a working bot.
Can I trade Polymarket from Telegram?
Third-party Telegram bots offer Polymarket trading, but most need your private key or a delegated key. Use only scoped, time-limited session keys, keep funds small, and prefer a private Telegram bot you control for alerts and pause commands.
A Polymarket trading bot in 2026 is a fee, latency and legal-access problem before it is a signal problem: build on CLOB V2 and pUSD, quote as a maker where you can, enforce hard risk limits, and automate only on venues you are allowed to use.