Polymarket trading, written by someone who actually trades it.
Mispricings, oracle lag, weather edges, and how to plug everything into Claude. No hype, no thread-bait — just what we've learned from running the strategies live.
Polymarket mispricing, explained: why share prices drift from the underlying (and how to spot it)
Polymarket markets resolve on real-world numbers — the Chainlink BTC price, the daily-high in NYC, the close in Tokyo. The share price between now and resolution doesn't track those numbers tick-for-tick. The gap is the trade. Here's where it comes from, when it appears, and how to measure it.
Chainlink oracle lag: the Polymarket crypto trade nobody talks about
Polymarket BTC and ETH markets resolve on Chainlink aggregators — and those aggregators update on a schedule, not tick-for-tick. When the underlying moves and the oracle hasn't caught up, the share price prices the wrong number. How big is the gap, when does it appear, and what's the structure of the trade?
Polymarket weather markets: a complete guide for traders
What weather markets are, how they resolve, where the edges live, and what data you actually need. We cover bias correction, the limits of GFS, why ECMWF wins on humid days, and how to integrate the whole thing with a trading bot — without building a meteorology team.
Build a Polymarket trading bot in Claude Code (MCP tutorial)
Plug datapolymarket's MCP server into Claude Code and you have a coding agent that can read live weather, query Chainlink lag, and write the strategy by chatting with you. No manual REST plumbing. Walkthrough with real prompts and a working bot at the end.
Why 90% of Polymarket bots lose: the data problem nobody admits
Polymarket bots fail because they trade on the same public data Polymarket itself prices on. If your inputs are the order book and the prices, you have no edge — you ARE the market. The fix is to trade on the underlying truth before it shows up as a price.