smithery.ai

polymarket-knowledge

Polymarket CLOB API knowledge base for order management, WebSocket events, and trading operations. Use when working with order lifecycle (place, fill, cancel), debugging WebSocket USER_TRADE/USER_ORDER events, understanding API field mappings, or implementing trading logic.

First seen Mar 25, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,365 B
  • docs SUMMARY.md 302 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

Polymarket Knowledge

Overview

Comprehensive reference for Polymarket CLOB API integration, focusing on order management and real-time event handling.

Quick Reference

Order Types

Type Behavior Use Case
GTC Good Till Cancelled Maker orders, liquidity provision
GTD Good Till Date Time-limited orders
FOK Fill Or Kill Must fill completely or cancel
FAK Fill And Kill Fill what you can, cancel rest

Order Requirements

  • Minimum order value: $1 USDC
  • Minimum shares: 5
  • Tick size: 0.01 (prices must be 0.01, 0.02, ... 0.99)

Order State Machine

See [references/order-state-machine.md](references/order-state-machine.md) for complete state diagram and transitions.

States: PENDING → OPEN → PARTIALLY_FILLED → FILLED/CANCELLED/EXPIRED

API Status Mapping:

  • live → OPEN
  • matched (partial) → PARTIALLY_FILLED
  • matched (full) → FILLED
  • delayed → PENDING
  • cancelled → CANCELLED
  • expired → EXPIRED

WebSocket Events

See [references/websocket-events.md](references/websocket-events.md) for field mappings and examples.

Key Endpoints:

  • Market: wss://ws-subscriptions-clob.polymarket.com/ws/market
  • User: wss://ws-subscriptions-clob.polymarket.com/ws/user (authenticated)

USERORDER Event Types: PLACEMENT, UPDATE, CANCELLATION USERTRADE Statuses: MATCHED, MINED, CONFIRMED, RETRYING, FAILED

Common Pitfalls

  1. Wrong field names: API uses matchedamount not matchedsize, sizematched not matchedsize
  2. Wrong endpoint: USER events require /ws/user, not /ws/market
  3. USDC type: Polymarket uses USDC.e (bridged), not native USDC

Resources

  • [references/order-state-machine.md](references/order-state-machine.md) - State transitions and validation
  • [references/websocket-events.md](references/websocket-events.md) - WebSocket field mappings
  • [references/api-field-mappings.md](references/api-field-mappings.md) - API response field reference