Market making on Polymarket is fundamentally different from directional trading strategies like sentiment analysis or momentum following. Instead of trying to predict which way a market will move, market makers provide liquidity by placing simultaneous buy and sell orders — offering to buy YES at $0.48 and sell YES at $0.52, for example. When both sides fill, you pocket the $0.04 spread without taking a directional bet.

Polymarket’s architecture makes it uniquely suited to automated market making. The platform uses a Central Limit Order Book (CLOB) rather than an AMM, which means market makers can place limit orders at precise prices and quantities — the same order book mechanics used in traditional financial exchanges. The Polymarket API provides full programmatic access to order placement, cancellation, and modification, enabling bots to manage quotes in real time.

The catch is that market making on prediction markets carries risks that do not exist in traditional finance. Events resolve to 0 or 1 (not a continuous range), breaking news can create instant 20-30 cent moves, and liquidity in most markets is thin enough that a single large order can move the price significantly. A good market-making bot must manage these prediction-market-specific risks while maintaining competitive spreads.

Here is the honest reality as of 2026: market making on Polymarket is a developer activity, not a subscription you buy. There is no independently verifiable turnkey “market-making bot” you can sign up for — the products advertised that way have no public track record or real users. What genuinely exists is Polymarket’s own open-source market-maker keeper, the official reference implementation you run yourself, plus general building blocks like pmxt for a custom or cross-platform maker. This guide is therefore framed honestly: it explains how prediction-market making works and its risks, then points you at the real, verifiable starting points instead of a paid product that does not exist.

The Real Polymarket Market-Making Tools (2026)

ToolTypeLicense / StarsStatusSource
Polymarket/poly-market-makerOfficial open-source MM keeperMIT (~303★)The canonical reference bot; not frequently updated (last significant push mid-2024)GitHub
pmxtUnified prediction-market API (SDK)MIT (~1,830★)Foundation for building a custom or cross-platform maker; activeGitHub

GitHub figures verified May 2026. Neither is a one-click product — both are code you run and configure yourself. Treat market making here as a build-it-yourself discipline where these are your starting scaffolds.

For broader context, see the overall bot rankings and the buyer’s guide.


What to Look for in a Market-Making Bot

1. Spread management sophistication. A naive market-making bot places fixed-width spreads and hopes for the best. A good bot dynamically adjusts spread width based on market volatility, time to event resolution, order book depth, and recent fill patterns. In calm markets, tighter spreads capture more volume. When volatility spikes (breaking news, approaching resolution), wider spreads protect you from adverse selection. The bot needs to make these adjustments in real time.

2. Inventory control. As a market maker, you will inevitably accumulate inventory — ending up net long or short on a market. Uncontrolled inventory accumulation is the primary way market makers lose money. Good bots skew their quotes to reduce inventory: if you are net long YES, the bot widens the ask (making it harder to buy more YES) and tightens the bid (making it easier to sell YES back). This dynamic skewing should be configurable with clear parameters.

3. CLOB integration quality. Market making lives and dies on execution speed. The bot needs tight integration with Polymarket’s CLOB API — fast order placement, instant cancellation, and atomic order modification. Bots that cancel and replace (two separate operations) instead of modifying in place (one operation) are at a disadvantage during fast markets. WebSocket-based real-time feeds are essential; polling-based bots are too slow.

4. News event handling. Prediction markets have a unique risk: a single news headline can move prices 20+ cents in seconds. Market-making bots must have a mechanism for detecting high-volatility events and either widening spreads dramatically or pulling quotes entirely until the market stabilizes. Bots without this capability will suffer heavy adverse selection losses during news events.

5. Multi-market support. Profitable market making in 2026 often requires providing liquidity across multiple markets simultaneously. The bot should support monitoring and quoting across many markets, with independent parameters for each, and aggregate inventory reporting across the portfolio.


Choosing Your Starting Point

These are not competing products to rank — they are two different starting points for a build-it-yourself effort:

  • You want the official reference and a working bot to runPolymarket/poly-market-maker. It is Polymarket’s own open-source keeper, so it speaks the CLOB natively and is the most authoritative example of how the platform expects a maker to behave. The trade-off: it has not been updated frequently, so expect to verify it against the current API and fill gaps yourself.
  • You are building a custom or cross-platform maker from scratchpmxt. It gives you one unified, actively maintained API across Polymarket, Kalshi, and Limitless, so you write your quoting and inventory logic against a single interface rather than hand-rolling each exchange client.

Either way, the hard parts — dynamic spreads, inventory skewing, adverse-selection protection during news events — are logic you implement. The sections below explain what that logic needs to do.


The Tools in Detail

Polymarket/poly-market-maker

Polymarket/poly-market-maker (~303★, MIT, verified May 2026) is the single most credible market-making tool for Polymarket precisely because it is Polymarket’s own. It is an open-source keeper bot — the reference implementation of an automated liquidity provider for the CLOB — published by the team that runs the exchange. If you want to understand how Polymarket intends market makers to place, refresh, and cancel quotes, this is the authoritative source.

The honest caveat is maintenance cadence: the repository’s last significant push was in mid-2024, so it predates more recent platform changes (for example, you should confirm its behavior against the current CLOB and collateral setup before trusting it with capital). It is also explicitly a developer tool — you clone it, configure spread and inventory parameters, supply your own credentials, and run it on your own infrastructure. There is no dashboard-as-a-service and no support desk. But as a free, MIT-licensed, officially-blessed starting point, nothing else on Polymarket matches it.

pmxt

pmxt (~1,830★, MIT, verified May 2026) is the “CCXT for prediction markets” — a single unified API spanning Polymarket, Kalshi, and Limitless. It is not a market maker by itself; it is the foundation you build one on. For anyone writing a custom maker, especially one that wants to quote the same event across more than one venue, pmxt removes the most tedious work: integrating each exchange’s authentication, order types, and data feeds separately.

Because it is actively maintained and MIT-licensed, pmxt is a safer base than an unmaintained bot if you intend to build something durable. You still implement all of the market-making logic — spread modeling, inventory control, news-event handling — but you do it once, against one interface, instead of per exchange. Pair it with the py-clob-client reference for the Polymarket-specific details.


How to Evaluate a Market-Making Setup

Before committing to a market-making bot, run through this testing checklist:

  • Paper trade on at least three different market types for two weeks. Market-making performance varies dramatically between calm, slow-moving markets and volatile, news-driven markets. Test across political events, sports, and economic indicators to understand where the bot performs best.
  • Measure the spread capture rate. Track what percentage of your quotes result in both sides filling (the “round trip” rate). A healthy market-making bot should complete round trips on 40-60% of quotes in moderately liquid markets. Below 30% suggests your spreads are too wide; above 70% suggests they may be too tight.
  • Stress-test inventory management during volatile events. Simulate or observe a news-driven price spike. Does the bot widen spreads? Pull quotes? Or keep quoting at stale prices and accumulate adverse inventory? Poor volatility handling is the fastest way to lose money as a market maker.
  • Verify order management reliability. Check that the bot correctly handles partial fills, failed cancellations, and API disconnections. If the CLOB API goes down for 30 seconds, does the bot gracefully pause and resume, or does it leave stale orders in the book?
  • Calculate net PnL after all costs. Market-making profits are thin. Ensure the bot’s reporting includes Polymarket fees, gas costs, slippage, and the cost of the bot itself. Gross spread captured can look healthy while net PnL is negative.
  • Compare against passive holding. As a sanity check, compare the bot’s return to simply holding USDC during the same period. Market making should outperform holding cash on a risk-adjusted basis — if it does not, the strategy is not working.

For the full evaluation framework, see the verification guide and the buyer’s guide.


Setup Guide: Getting Started with Market Making on Polymarket

Step 1: Fund your Polymarket wallet with meaningful capital. Market making requires more capital than directional trading. Start with at least $5,000 in USDC on Polygon. With less than $5,000, your spreads need to be so wide to cover costs that you will rarely get filled. For wallet setup, see the Polymarket quickstart.

Step 2: Choose your initial markets carefully. Do not start market making on the most popular, competitive markets (major election outcomes, high-profile events). Choose moderately liquid markets with enough volume to generate fills but not so much competition that your spreads are immediately undercut. Lower-profile political events, niche sports markets, and longer-dated contracts are good starting points.

Step 3: Set up API access with appropriate permissions. Generate Polymarket API keys with full trading permissions. For self-hosted bots, store credentials in environment variables — never hardcode them. Review the Polymarket API guide and the rate limits guide to ensure your bot operates within platform limits.

Step 4: Configure conservative initial parameters. Start with: spread width of 5-8 cents (wider than you think you need), maximum inventory of 15-20% of capital per market, linear skew coefficient of 0.5 (moderate inventory mean-reversion), and order refresh every 5 seconds. You can tighten spreads after you understand the competitive dynamics of your chosen markets.

Step 5: Paper trade for at least two weeks. Market making rewards patience and observation. During paper trading, track your fill rates, inventory patterns, PnL by time of day, and how the bot behaves during news events. Identify which markets and time periods are most profitable.

Step 6: Go live on one market first. Start with a single market using 20-30% of your intended capital. Monitor closely for the first week — pay special attention to how the bot handles its first real news event. Market making feels mechanical during calm periods and chaotic during volatile ones; you need to experience both before scaling.

Step 7: Scale gradually across markets. As you gain confidence, add markets one at a time. Each new market needs its own spread and inventory parameters — copy-pasting parameters from one market to another will underperform versus per-market tuning. Aggregate your portfolio exposure across all markets to ensure total risk stays within your tolerance.