Case Study: Inside the Polymarket Run That Made 500% in 2 Days
A settlement-only case study of a real OpenClawCash Polymarket agent run: account mapping, guardrails, execution order, and the basis for a 500% result.
Inside the Run: How Our Polymarket Agent Made 500% in 2 Days
One short trading window delivered roughly 500% in two days. This post is the case study, not the setup guide — if you want the connect/fund/trade walkthrough, see the Polymarket venue update.
The headline is exciting, but the useful part is what happened operationally during the run: a clean agent execution setup, strict account mapping, and guardrails that kept the system controllable while the agent executed autonomously.
The Setup Going Into the Run
Before the first order went out, the agent had:
- A funded Polymarket venue wallet with a conservative per-trade cap and daily spending limit already active
- Read access confirmed first, trade access enabled only after account mapping checked out
- A fixed analytics basis agreed in advance, so results couldn't be reinterpreted after the fact
That last point matters more than it sounds. Locking in the measurement approach before trading starts is what keeps a good run honest.
What the Agent Actually Did
Across the window, the agent executed the full prediction-market loop end to end, repeatedly:
- checked wallet and account status before every decision
- resolved market and outcome selections
- ranked opportunities and sized positions inside its per-trade cap
- placed multiple Polymarket orders in sequence
- verified matched status and confirmations
- tracked exposure and redeemed winning positions as markets resolved
The pattern repeated cleanly: rank, size, execute, confirm. There was no manual overhead between phases, and no ambiguity about where to check state after an action.
Example Prompt Sequence Used During the Run
$ check my polymarket wallet + account status and show available buying power
$ find high-conviction opportunities and rank top setups by risk/reward
$ resolve each market slug + valid outcomes before placing any order
$ place 4 orders with explicit size and price limits, then report matched vs unfilled
$ show tx confirmations, updated exposure, and post-trade account state
Validate state first, execute with explicit constraints, then verify outcomes. That sequence, repeated without deviation, is most of the edge.
Why the Result Held Up Under Scrutiny
Execution clarity is what made the outcome trustworthy rather than a lucky screenshot:
- order responses returned usable success states
- matched versus non-fill status was immediately visible
- post-trade state was quick to verify against the wallet, not just the dashboard
The Analytics Basis Behind the 500% Figure
We use settlement-only analytics (Claimed / Lost) as the canonical basis for this result — not open exposure, not mark-to-market on unresolved positions.
That means the figure reflects:
- Win Rate, based on settled outcomes only
- PnL and Avg PnL %, computed after settlement
- No credit taken for positions still open when the window closed
Mixing open exposure with settlement outcomes is the most common way a trading result gets overstated. This run's number is settlement-only on purpose.
What This Run Does and Doesn't Prove
It proves an agent can run a full Polymarket execution loop unattended, inside guardrails, without manual intervention, and produce a verifiable settled result.
It does not prove the strategy generalizes, that 500% is a repeatable rate, or that guardrails alone guarantee profitability. Two days is a small sample. Treat this as evidence the execution layer holds up under real conditions, not as a forecast.
Practical Takeaway
If you're evaluating whether an agent can be trusted to trade Polymarket unattended, the operational details here (account mapping enforced before trade access, caps active before the first order, one settlement-only metric basis) are the parts worth copying. The specific return is a data point, not a promise.
Want to set up the venue yourself? The Polymarket venue update covers the current connect-fund-trade flow, guardrails, and supported assets in full.
Frequently Asked Questions
How long does setup usually take? For most users, first-time setup takes under 3 minutes if wallet and funder account mapping is correct.
What breaks most often on first attempt? The most common issue is signer address and Polymarket funder address mismatch. Verify both explicitly in Venue Settings.
Why use settlement-only metrics instead of mixed activity? Settlement-only (Claimed/Lost) keeps win/loss and PnL consistent across cards and charts and avoids mixed-semantic reporting.
Can I run this with small size first? Yes. You can start with small size, but connection validation itself is confirmed by successful venue setup.
Risk Disclosure
Prediction-market trading carries real financial risk. Past performance, including the result described here, does not guarantee future results. Position sizing and guardrails are mandatory, not optional. This post is a case study, not financial advice.