Bot for Polymarket
Start with residency, not a repo
Before you clone anything, answer one question: which access path are you on? A US person should start from Polymarket US documentation — not from a CLOB tutorial that never mentions KYC or polymarket.us.
| US path | International path | |
|---|---|---|
| Docs / hosts | api.polymarket.us, gateway.polymarket.us | International CLOB tutorials dominate GitHub |
| KYC / account | US-specific onboarding | Different eligibility rules |
| Fee schedule | US schedule; verify standard and product-specific fees | Do not assume US numbers apply |
| Bot risk | Using International tooling as a US person | Assuming US fee tables / docs |
Operator checklist (do this in order)
- Confirm residency and product path — US vs International is a product constraint, not a preference.
- Open the matching docs — if the tutorial never mentions
polymarket.us, treat it as International-first until proven otherwise. - Authenticate read-only — list markets before any order loop.
- Model fees on that path — see updated US fee guide.
- Paper or tiny size — never go from “hello world” to full size. See paper mode & risk.
What Telegram and listicles get wrong
“One bot for everyone” is marketing. Access is not universal. A SaaS that only wires International CLOB flows is not a US product. A GitHub repo with stars is not a residency certificate.
When you diligence a tool, use the Trust & Diligence Desk checklist — especially residency support and keys.
How this maps to Bot for Polymarket
Bot for Polymarket publishes research and offers a waitlist for a planned hosted builder. We treat venue access as a first-class product constraint: waitlist updates track path support, not vibes. We do not claim every path is live for every user today — we claim we will not paper over the difference.
Fee references and product status updated October 7, 2026: Polymarket US fee schedule.
Part of the Polymarket trading bots handbook.