Polymarket

Prediction market integration via Gamma and CLOB-aware provider actions. Setup, preflight, and EU egress for live orders.

Category: Prediction

Polymarket flows use governed catalog actions with CLOB prep and policy gates in the runtime. Live orders egress through EU infrastructure, not from the Hermes machine region alone.

Credential model

LayerModel
Owner signerUser Privy embedded wallet in production
Signer delegationUser grants Thirdfy signer access via Privy
CLOB credentialsEncrypted polymarket_clob stored in Thirdfy API after browser setup
Deposit walletDeterministic funder with signatureType=3 (POLY_1271) for new users
CollateralDeposit-wallet pUSD for CLOB buying power. Signer EOA USDC is not CLOB buying power.

Wallet, funder, and CLOB credentials must belong together. ERC-7710/Gator applies to EVM paths, not CLOB order signing.

Discovery

curl "https://api.thirdfy.com/api/v1/agent/actions/catalog"
SurfaceExample
MCPgetProviderActions { provider: "polymarket" }
CLIthirdfy-agent actions with polymarket filter

Readiness checklist

  • Browser or Privy setup flow completed for the owner wallet.
  • CLOB credentials stored and valid before autonomous order placement.
  • Setup, preflight, and geoblock gates pass in production runtimes.
  • Credits gate orchestration; deposit-wallet pUSD funds the trade.
  • Gasless relayer steps for deposit-wallet deploy and approvals where applicable.

Execution lanes

runModeNotes
thirdfy / hybridDelegated user capital with stored CLOB creds
agent_walletAgent-owned lane when policy and setup allow

See Delegation and protection for lane boundaries.

MCP sequence (summary)

  1. getProviderActions { provider: "polymarket" }
  2. Gamma discovery (tags, events, markets)
  3. CLOB setup and readiness actions
  4. Place or cancel orders with managed venue credentials

See Thirdfy MCP.

Hosted deploy

Polymarket signal templates are on EarnClaw (docs.earnclaw.com).