--- url: "https://predictiontoolkit.com/tools/poly-maker/" publisher: "PredictionToolkit" dateModified: "2026-11-03" --- [← Liquidity & market making]() Trading bot # poly-maker: Maker-Only Polymarket Bot with Paper Mode poly-maker is a configurable Python/CLI Polymarket market-making bot. It scans political markets and manages post-only BUY-YES and BUY-NO quotes with inventory-aware prices and size. [**3.5**/ 5Editorial rating]() [Editorial assessment]() [Open the maintainer's poly-maker repository]() github.com **Available on:** CLI **Pricing:** The repository is MIT-licensed. Infrastructure, funding transactions and applicable venue fees are separate. [Screenshots]() [Explore alternatives]() [Liquidity & market making]() [Trading bots]() +3 more [Paper trading]() [Risk management]() [Market scanners]() ## Screenshots and interface Product preview1 / 2 Repository overview of the quoting engine and requirements. ## What is poly-maker? The documented CLOB V2 engine reconciles quotes with live orders and changes behavior across quiet, trending, event, reduce-only and halted regimes. TOML stores configuration; SQLite and an event journal retain state for investigating quote decisions. Use --paper for the live-feed pipeline without posting orders. Historical replay over journals is not implemented, and external polling, news and cross-venue inputs are not built in. A filled complementary pair differs from one-sided inventory. Neither live nor paper execution or safeguard effectiveness was tested for this profile. ### Who it is for - Developers studying market making. - Operators wanting local configuration and journals. - Users evaluating reward-aware market selection. ## Features and coverage - **Scanner** Rank political markets using rewards, rebates and risk inputs. - **Maker-only quotes** Post-only orders and live-order reconciliation. - **Inventory skew** Lean prices and reduce size near exposure caps. - **Regimes** Quiet, trending, event, reduce-only and halted behavior. - **Operating controls** Exposure limits, daily-loss kill switch, stale-feed halt and heartbeat handling. - **Paper pipeline** Use the live feed without posting orders. - **Local state** TOML settings, SQLite state and event journals. ## Workflows with poly-maker ### Evaluate a profile Scan markets, select a small set and run paper mode. Inspect quotes across volatility and inventory states. ### Operate a market Perform wallet preflight, apply a profile and monitor positions, orders and kill-switch state. ### Explain a quote change Read the journal and state to investigate widening, regime changes or cancellation. ## Pricing and total cost The repository is MIT-licensed. Infrastructure, funding transactions and applicable venue fees are separate. ## Getting started **Before you start:** External polling, news and cross-venue inputs are not included. 1. Use Python 3.12 or newer and the documented uv installation. 2. Configure wallet identity and TOML. 3. Scan and select markets. 4. Run --paper. 5. Use doctor to inspect wallet readiness before live orders. 6. Monitor status and keep cancel-all available. Historical replay over recorded journals is not implemented. ## Useful links ### What to check - External polling, news and cross-venue inputs are not included. - Safe/proxy merging is not wired; these inventory exits use limit sells. - livetest posts an order and moneydoctor performs real trades; neither is read-only. - A complementary pair and a one-sided position have different exposure. A closer look ## Ratings & reviews Editorial rating **3.5**/ 5 0 user reviews PredictionToolkit editorial ### Our take on poly-maker poly-maker is a substantial code reference for studying how paper quotes and inventory controls fit into a maker strategy. Its operating limits are documented, but journal replay is unfinished and some commands place real orders. Those boundaries make supervised configuration important rather than demonstrating safeguard effectiveness. 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]() ![Marketlens Python installation and Strategy quickstart]() ![Marketlens Python SDK logo]()[Marketlens Python SDK]() SDK**4.0**Editorial Compare fast bar experiments with detailed L2 replay, reusing downloaded history between strategy changes. - Language Python Use a separate historical replay engine. ![NautilusTrader Polymarket adapter scope and integration-guide entry]() ![NautilusTrader logo]()[NautilusTrader]() SDK**4.0**Editorial Receive native market events and manage signed orders, reconciliation and resolution in one trading framework. - Language Python · Rust Compare a general event-driven trading framework. ![PolyScalping documentation overview with an interface preview]() ![PolyScalping logo]()[PolyScalping]() Analytics**3.5**Editorial Save market scans, compare wallets and track the rewards behind liquidity provision. - Access Web Compare a user-facing rewards and market-making toolkit. ## Frequently asked questions about poly-maker ### Does the main engine cross the spread? It uses post-only orders. ### Can I avoid submitting orders? Yes. Run --paper. ### Is historical backtesting included? No. Journal replay is listed as unfinished. ### Why quote both YES and NO buys? The strategy acquires complementary legs and manages combined inventory and entry cost. In this profile