Bot for Polymarket
Cluster · Handbook hub
Polymarket US vs International for bots
Polymarket is not one API. US and International are different access paths — and most “how to build a Polymarket bot” posts quietly assume the International path.
If you route wrong, nothing else in your stack matters. Fee math, signal quality, and your favorite GitHub repo all fail the same way: the surface you built against is not the one you are allowed to use.
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 (Θ moved July 1, 2026) | 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 July 2026 US fee note.
- 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 is a hosted no-code builder for Polymarket operators. 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.
Part of the Polymarket trading bots handbook.
Venue Access Desk · Updated 2026-07-08