PolytoolhubWhat is poly-maker?
Poly-maker is a local Python market-making engine focused on political markets. It discovers candidates through Gamma, maintains live books and reconciles a target quote set with working orders. The strategy uses fair value, inventory, volatility and adverse-selection estimates to change quote prices and size.
Who it is for
- Developers researching automated market making
- Operators who want local configuration and event journals
- Users evaluating reward-aware market selection
Features and coverage
- Available on
- Python, CLI
- Markets & venues
- Polymarket
- Research topics
- Politics, Market making
- Market scanner
Rank political markets using rewards, rebates and market-risk inputs.
- Post-only execution
Submit maker-only quotes and reconcile them with live orders.
- Inventory skew
Lean prices and taper size as exposure approaches caps.
- Regime handling
Change behavior across quiet, trending, event, reduce-only and halted states.
- Operational controls
Use exposure limits, daily-loss kill switch, stale-feed halts and heartbeat handling.
- Paper pipeline
Run against the live feed without posting orders.
- Local state
Keep configuration in TOML and state in SQLite with an event journal.
Workflows with poly-maker
Evaluate a quote profile
Scan markets, select a small list and run the full pipeline in paper mode. Inspect quote changes under different volatility and inventory states.
Operate a configured market
Run the wallet preflight, apply the chosen profile and monitor positions, open orders and kill-switch state.
Investigate an event
Use the recorded journal and state to understand why quotes widened, changed regime or were canceled.
Pricing and total cost
The repository is MIT-licensed. Infrastructure, funding transactions and applicable venue fees remain separate.
Getting started
Before you start: The replay backtester over recorded journals is not implemented.
- Use Python 3.12 or newer and install with the documented uv workflow.
- Configure wallet identity and TOML settings.
- Scan and select markets.
- Run with --paper.
- Inspect wallet readiness with doctor before enabling live orders.
- Monitor status and keep cancel-all available for the operator.
Useful links
What to check
- The replay backtester over recorded journals is not implemented.
- External polling, news and cross-venue inputs are not built into the documented strategy.
- Safe/proxy merging is not wired in the described implementation; those inventory exits use limit sells.
- livetest posts an order, and moneydoctor performs real trades; neither is a read-only check.
- A filled complementary pair and a one-sided inventory position have different exposure.
A closer look
Ratings & reviews
User reviews 0
The main score switches to user ratings after 5 published reviews.
A specific example helps the next person choose the right tool.
Write a review
How was your experience with poly-maker?
Share what you used, what worked and what could be better. We confirm your email and review the submission before publishing.
To submit a review, email info@polytradingbot.com with the tool name, your rating and your experience. Enable JavaScript to prepare a draft here.
Related tools
Browse category
Retrieve historical Polymarket books and run either tick-level execution simulations or faster bar-based signal backtests in Python.
- Language Python
Use a Rust-native Polymarket adapter inside NautilusTrader for live feeds, signed execution and strategy research.
- Language Python · Rust
Scan markets, compare trader rankings and separate trading earnings from liquidity rewards.
- Access Web
Frequently asked questions about poly-maker
Does it cross the spread to enter?
The main quoting engine uses post-only orders.
Can I run the pipeline without submitting orders?
Yes. Use --paper.
Is a historical backtester included?
The README lists replay backtesting as unfinished.
Why can both YES and NO be bids?
The strategy acquires complementary outcome legs and manages their combined inventory and entry cost.