Polymarket Knowledge
Developmentpolymarket-knowledgePolymarket Knowledge is an Agent Skill for development published in the cyl19970726/poly-sdk repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
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.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/cyl19970726/poly-sdk/blob/HEAD/.claude/skills/polymarket-knowledge/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/polymarket-knowledge, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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 for complete state diagram and transitions.
States: PENDING → OPEN → PARTIALLY_FILLED → FILLED/CANCELLED/EXPIRED
API Status Mapping:
live→ OPENmatched(partial) → PARTIALLY_FILLEDmatched(full) → FILLEDdelayed→ PENDINGcancelled→ CANCELLEDexpired→ EXPIRED
WebSocket Events
See 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)
USER_ORDER Event Types: PLACEMENT, UPDATE, CANCELLATION USER_TRADE Statuses: MATCHED, MINED, CONFIRMED, RETRYING, FAILED
Common Pitfalls
- Wrong field names: API uses
matched_amountnotmatched_size,size_matchednotmatched_size - Wrong endpoint: USER events require
/ws/user, not/ws/market - USDC type: Polymarket uses USDC.e (bridged), not native USDC
Resources
- references/order-state-machine.md - State transitions and validation
- references/websocket-events.md - WebSocket field mappings
- references/api-field-mappings.md - API response field reference