Use when the user wants to actually PLACE, manage, or redeem bets on Polymarket (not just read odds — that's the blockrun_predexon_* data tools). Covers setup (deposit wallet, funding, approvals), buy/sell with confirm gating, positions, redeeming winnings, geoblock handling, and the end-to-end flow.
80
100%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Medium
Suggest reviewing before use
Real-money trading on Polymarket's CLOB V2 (Polygon), signed locally by the
user's ClawRouter wallet key. Data discovery stays on the
blockrun_predexon_* tools — blockrun_polymarket only trades.
~/.openclaw/blockrun/wallet.key, or
BLOCKRUN_WALLET_KEY) — the SAME wallet that pays for LLM calls. Never leaves
the machine.confirm:true + caps do.setup ClawRouter bootstraps a builder key from the user's OWN wallet, then
derives + deploys the vault (all gasless). Geoblock is handled by default —
CLOB traffic routes through BlockRun's Tokyo egress out of the box.confirm:true unless the user explicitly approved that exact
trade. Call once WITHOUT confirm → show the dry-run preview → ask → re-call
with confirm:true.POLYMARKET_MAX_BET_USD (default $25) and optional session cap
are enforced locally; don't try to split orders to sneak past them.# 0. No Polymarket account or API keys needed — ClawRouter bootstraps everything
# from the user's own wallet on first setup. (Set POLYMARKET_CLOB_HOST to a
# permitted-region egress only if the user is in a geoblocked region.)
# 1. Provision + inspect (idempotent, safe to re-run any time)
blockrun_polymarket action:"setup"
# → deposit wallet address + funding instructions + region status
# 2. Fund the vault from the user's Base USDC — gasless x402, one call ($0.01 fee,
# non-custodial). pUSD credit is ASYNC (minutes) — re-run setup to watch it. Min $2.
blockrun_polymarket action:"fund" amount_usd:5 # dry-run preview
blockrun_polymarket action:"fund" amount_usd:5 confirm:true
# 3. Sign the one-time gasless approval batch (after user consent)
blockrun_polymarket action:"setup" confirm:true
# 4. Find a market + token (data tool, paid data)
blockrun_predexon_markets ... # → clobTokenIds, conditionId (Polymarket /v1/pm data)
# 5. Preview, then place
blockrun_polymarket action:"buy" token_id:"..." amount_usd:2 # dry-run
blockrun_polymarket action:"buy" token_id:"..." amount_usd:2 confirm:true # market FOK
# or limit: price:0.45 size:10 (GTC; order_type:"GTD" + expires_at for expiry)
# or via condition: condition_id:"0x..." outcome:"Yes"
# 6. Manage
blockrun_polymarket action:"orders" # open orders
blockrun_polymarket action:"cancel" order_id:"..." # or all:true
blockrun_polymarket action:"positions" # holdings + PnL + redeemable
# 7. Claim winnings after resolution (gasless)
blockrun_polymarket action:"redeem" condition_id:"0x..." # preview
blockrun_polymarket action:"redeem" condition_id:"0x..." confirm:true
# 8. Cash out — pUSD → native USDC on Base, back to the user's agent wallet
blockrun_polymarket action:"withdraw" # dry-run (full balance)
blockrun_polymarket action:"withdraw" confirm:true # (partial: amount_usd:5)amount_usd (dollars). Market sell = size (shares).price + size; default GTC; post_only:true for maker-only.Order placement is IP-geoblocked (US/UK/EU + many regions). Handled by
default — CLOB traffic routes through BlockRun's Tokyo egress, so setup
reports ✅ Region: order placement permitted out of the box; you don't need to
do anything. A user can override with POLYMARKET_CLOB_HOST (their own relay),
or POLYMARKET_CLOB_PROXY / HTTPS_PROXY. Respecting Polymarket's ToS for the
user's jurisdiction is the user's responsibility — never suggest evading it.
action:"setup"./wallet command (or set
BLOCKRUN_WALLET_KEY) before trading.setup. (Advanced: POLYMARKET_SIG_TYPE=0 =
plain EOA mode; needs POL gas + pUSD in the EOA, and is read-only for orders.)setup again (refreshes the
CLOB's balance cache).setup, then consider
POLYMARKET_SIG_TYPE=0 (upstream clob-client-v2 issue #65).c6587c1
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.