polymarket

Query Polymarket REST endpoints and convert event data into readable odds.

87|20|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/openaeon/OpenAEON --skill polymarket-openaeon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: polymarket
Source: https://github.com/openaeon/OpenAEON/tree/main/skills/polymarket
Command: npx skills add https://github.com/openaeon/OpenAEON --skill polymarket-openaeon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It solves the need to quickly understand prediction-market odds by retrieving current prices, orderbook depth, and historical price movements from Polymarket’s public APIs.

Core Features & Use Cases

  • Market search and discovery: Find relevant events and their nested markets from a user query.
  • Odds and volume reporting: Convert Polymarket outcomePrices into readable probability percentages and show available volume.
  • Price & depth retrieval: Pull real-time price and orderbook data using CLOB token IDs.
  • Price history lookup: Retrieve probability time series using conditionId for deeper context.
  • Use Case: When someone asks, What are the odds of this specific outcome, or how has the probability moved recently, this skill returns the market question, current probabilities, and (if requested) history and orderbook data.

Quick Start

Use the polymarket skill to search for markets matching the query bitcoin and summarize the top results with current Yes/No probabilities.

Frequently Asked Questions about polymarket

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get current odds and probabilities from Polymarket prediction markets?

To get current odds from Polymarket, you query public REST endpoints to retrieve event and market data, then transform double-encoded outcomePrices fields into readable probability percentages for Yes/No outcomes.

What is the process for retrieving Polymarket orderbook depth using CLOB token IDs?

Retrieving Polymarket orderbook depth requires mapping Gamma discovery outputs to CLOB pricing inputs using token_id, then querying CLOB endpoints to pull real-time price and orderbook data for the specified market tokens.

Can I find specific Polymarket events by searching with natural language questions?

Yes, Polymarket market search and discovery works by querying Gamma discovery endpoints with natural language questions to find and return matching events along with their nested market structures.

How do I pull probability price history for a specific Polymarket conditionId?

You pull probability time series history by mapping the conditionId from Gamma discovery outputs to CLOB history endpoints, retrieving historical price movements for a specific outcome condition from Polymarket public APIs.

Why does parsing Polymarket API responses require handling double-encoded JSON fields?

Parsing Polymarket API responses requires handling double-encoded JSON because fields like outcomePrices, outcomes, and clobTokenIds are returned as encoded strings within the JSON payload and must be decoded to map to CLOB inputs.