Scan a resolved Polymarket market for wallets exhibiting suspicious trading patterns: fresh funding, single-market focus, extreme ROI, late entry at high prices.

Authentication Browser login requests nansen:api for API key equivalent account API permissions; existing OAuth/MCP nansen:read semantics and separate wallet authorization are unchanged. Before any research command or loop, require an explicitly selected API key or saved browser session. Run nansen auth status first. Its cached/unverified metadata does not prove credential validity or unlocked storage. Cached access token expiry alone does not mean the session is unusable: the CLI normally renews a selected session automatically during an already authorized research task, without another consent request or a separate account check. Stop on anonymous selection, invalid authentication state, blocked or uncertain renewal/cleanup, or an actual authentication failure, including rejected or expired refresh authority. Follow the CLI error guidance; use the free nansen account check when troubleshooting calls for it. Do not unset a failed key, erase a session or switch to anonymous access to retry. Use nansen login for fresh browser approval within the documented platform scope, or configure a conventional API key. NANSEN API KEY overrides the saved session. OpenClaw's optional primaryEnv mapping preserves configured API key injection; it is not a required key gate or proof of authentication. Normal credits and entitlements apply. Login does not purchase credits. Browser login is enabled in production within the [documented platform scope](https://github.com/nansen ai/nansen cli/blob/main/docs/browser login.md preview platform scope). API keys and browser sessions use the same automatic x402 payment behavior: a supported HTTP 402 challenge can spend funds from the configured wallet under existing wallet authorization, payment policy and spending limits. Each call, including calls in loops, can incur a payment. Authentication, authorization and session renewal failures never trigger payment; login verification and nansen account never pay automatically. Anonymous x402 remains available as a separate paid workflow requiring explicit user intent and payment setup. Do not run this research workflow anonymously or switch to anonymous access after authentication fails. PM Suspicious Wallet Scanner Answers: "Are there wallets with suspicious trading patterns in this Polymarket market?" For each winner, compute ROI = total pnl usd / net buy cost usd 100 (skip ROI flags if net buy cost usd <= 0), then score (0–13). Within each tier group, apply only the highest matching flag: Flag Pts Trigger NEW WALLET 3 First funded within 7 days of now YOUNG WALLET 1 First funded 8–28 days ago (skip if NEW WALLET fires) SINGLE MARKET 3 trades by address shows only 1 distinct market id FEW MARKETS 1 2–3 distinct market ids (skip if SINGLE MARKET fires) EXTREME ROI 3 ROI = 500% HIGH ROI 2 ROI 200–499% (skip if EXTREME ROI fires) LATE ENTRY 2 Any trade on this market at price = 0.80 LARGE POSITION 2 net buy cost usd = $10k KNOWN ENTITY 2 Has Nansen labels Flagged at score = 3. High risk at = 7. High confidence suspicious pattern: NEW WALLET + SINGLE MARKET + EXTREME ROI (score 9+). If owner address is invalid (e.g. "0x"), use the proxy address for profiler calls too. If historical balances returns no records with value usd 0, the wallet may predate the 365 day window — treat wallet age as unknown and skip NEW WALLET / YOUNG WALLET flags. Pause ~1.5s between wallets to avoid rate limits. Skip wallets that error and continue scanning.

nansen-polymarket-insider-scan