Polymarket Comprehensive Skill

When to Use This Skill

• Working with Polymarket prediction markets
• Using Polymarket API for market data
• Implementing trading strategies
• Building applications with Polymarket services
• Learning Polymarket best practices

• Connecting to Polymarket's WebSocket service
• Building prediction market monitoring tools
• Processing live trades, orders, and market updates
• Monitoring market comments and social reactions
• Tracking RFQ (Request for Quote) activity
• Integrating crypto price feeds

Quick Reference

Real-Time Data Client Setup

npm install @polymarket/real-time-data-client

import { RealTimeDataClient } from "@polymarket/real-time-data-client";

const onMessage = (message: Message): void => {
    console.log(message.topic, message.type, message.payload);
};

const onConnect = (client: RealTimeDataClient): void => {
    client.subscribe({
        subscriptions: [{
            topic: "activity",
            type: "trades"
        }]
    });
};

new RealTimeDataClient({ onMessage, onConnect }).connect();

Supported WebSocket Topics

activity

• trades

  - Completed trades

• orders_matched

  - Order matching events
• Filters:

  {"event_slug":"string"}

  OR

  {"market_slug":"string"}

comments

• comment_created

  ,

  comment_removed

• reaction_created

  ,

  reaction_removed

• Filters:

  {"parentEntityID":number,"parentEntityType":"Event"}

rfq

• Request/Quote lifecycle events
• No filters, no auth required

crypto_prices

crypto_prices_chainlink

• update

  - Real-time price feeds
• Filters:

  {"symbol":"BTC"}

  (optional)

clob_user

• order

  - User's order updates

• trade

  - User's trade executions

clob_market

• price_change

  - Price movements

• agg_orderbook

  - Aggregated order book

• last_trade_price

  - Latest prices

• market_created

  ,

  market_resolved

Authentication for User Data

client.subscribe({
    subscriptions: [{
        topic: "clob_user",
        type: "*",
        clob_auth: {
            key: "your-api-key",
            secret: "your-api-secret",
            passphrase: "your-passphrase"
        }
    }]
});

Common Use Cases

client.subscribe({
    subscriptions: [{
        topic: "activity",
        type: "trades",
        filters: `{"market_slug":"btc-above-100k-2024"}`
    }]
});

client.subscribe({
    subscriptions: [{
        topic: "clob_market",
        type: "price_change",
        filters: `["100","101","102"]`
    }]
});

client.subscribe({
    subscriptions: [{
        topic: "comments",
        type: "*",
        filters: `{"parentEntityID":12345,"parentEntityType":"Event"}`
    }]
});

Reference Files

references/

• api.md - Polymarket API documentation
• getting_started.md - Getting started guide
• guides.md - Development guides
• learn.md - Learning resources
• trading.md - Trading documentation
• other.md - Additional resources

• README.md - WebSocket client API and examples
• llms.md - LLM integration guide
• llms-full.md - Complete LLM documentation

view

Key Features

Best Practices

WebSocket Connection Management

• Use

  onConnect

  callback for subscriptions
• Implement reconnection logic for production
• Clean up with

  disconnect()

  when done
• Handle authentication errors gracefully

Subscription Strategy

• Use wildcards (

  "*"

  ) sparingly
• Apply filters to reduce data volume
• Unsubscribe from unused streams
• Process messages asynchronously

Performance

• Consider batching high-frequency data
• Use filters to minimize client processing
• Validate message payloads before use

Requirements

• Node.js: 14+ recommended
• TypeScript: Optional but recommended
• Package Manager: npm or yarn

Resources

Official Links

• Polymarket Platform: https://polymarket.com
• Real-Time Client Repo: https://github.com/Polymarket/real-time-data-client
• API Documentation: See references/api.md

Working with This Skill

getting_started.md

api.md

trading.md

README.md

llms.md

llms-full.md

Notes

• Real-Time Client is TypeScript/JavaScript (not Python)
• Some WebSocket topics require authentication
• Use filters to manage message volume effectively
• All timestamps are Unix timestamps
• Market IDs are strings (e.g., "100", "101")
• Platform documentation covers both REST API and WebSocket usage