polymarket
Query Polymarket prediction market data — search markets, get prices, orderbooks, and price history. Read-only via public REST APIs, no API key needed.
Best use case
polymarket is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Query Polymarket prediction market data — search markets, get prices, orderbooks, and price history. Read-only via public REST APIs, no API key needed.
Teams using polymarket should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/polymarket/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How polymarket Compares
| Feature / Agent | polymarket | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Query Polymarket prediction market data — search markets, get prices, orderbooks, and price history. Read-only via public REST APIs, no API key needed.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Polymarket — Prediction Market Data Query prediction market data from Polymarket using their public REST APIs. All endpoints are read-only and require zero authentication. See `references/api-endpoints.md` for the full endpoint reference with curl examples. ## When to Use - User asks about prediction markets, betting odds, or event probabilities - User wants to know "what are the odds of X happening?" - User asks about Polymarket specifically - User wants market prices, orderbook data, or price history - User asks to monitor or track prediction market movements ## Key Concepts - **Events** contain one or more **Markets** (1:many relationship) - **Markets** are binary outcomes with Yes/No prices between 0.00 and 1.00 - Prices ARE probabilities: price 0.65 means the market thinks 65% likely - `outcomePrices` field: JSON-encoded array like `["0.80", "0.20"]` - `clobTokenIds` field: JSON-encoded array of two token IDs [Yes, No] for price/book queries - `conditionId` field: hex string used for price history queries - Volume is in USDC (US dollars) ## Three Public APIs 1. **Gamma API** at `gamma-api.polymarket.com` — Discovery, search, browsing 2. **CLOB API** at `clob.polymarket.com` — Real-time prices, orderbooks, history 3. **Data API** at `data-api.polymarket.com` — Trades, open interest ## Typical Workflow When a user asks about prediction market odds: 1. **Search** using the Gamma API public-search endpoint with their query 2. **Parse** the response — extract events and their nested markets 3. **Present** market question, current prices as percentages, and volume 4. **Deep dive** if asked — use clobTokenIds for orderbook, conditionId for history ## Presenting Results Format prices as percentages for readability: - outcomePrices `["0.652", "0.348"]` becomes "Yes: 65.2%, No: 34.8%" - Always show the market question and probability - Include volume when available Example: `"Will X happen?" — 65.2% Yes ($1.2M volume)` ## Parsing Double-Encoded Fields The Gamma API returns `outcomePrices`, `outcomes`, and `clobTokenIds` as JSON strings inside JSON responses (double-encoded). When processing with Python, parse them with `json.loads(market['outcomePrices'])` to get the actual array. ## Rate Limits Generous — unlikely to hit for normal usage: - Gamma: 4,000 requests per 10 seconds (general) - CLOB: 9,000 requests per 10 seconds (general) - Data: 1,000 requests per 10 seconds (general) ## Limitations - This skill is read-only — it does not support placing trades - Trading requires wallet-based crypto authentication (EIP-712 signatures) - Some new markets may have empty price history - Geographic restrictions apply to trading but read-only data is globally accessible
Related Skills
test-oversized-skill
A test fixture skill that exceeds 200 lines with multiple H2/H3 sections for split testing.
interactive-report-generator
Generate interactive HTML reports with Plotly visualizations from data analysis results. Supports dashboards, charts, and professional styling.
data-validation-reporter
Generate interactive validation reports with quality scoring, missing data analysis, and type checking. Combines Pandas validation, Plotly visualization, and YAML configuration for comprehensive data quality reporting.
agent-os-framework
Generate standardized .agent-os directory structure with product documentation, mission, tech-stack, roadmap, and decision records. Enables AI-native workflows.
OrcaFlex Specialist Skill
```yaml
repo-ecosystem-hygiene
Interpret the daily read-only repo ecosystem hygiene audit and route remediation through approved workflows.
domain-knowledge-sweep
Systematic multi-source research of an engineering domain. Spawns parent issue → 6 research subissues (Standards, Academic, Industry, LinkedIn-marketing, Code-audit, Synthesis) → gap implementation subissues. Replaces LinkedIn-only extraction with defensible comprehensive sourcing.
subagent-write-verification
Independently verify subagent-claimed file writes with filesystem and git checks before treating the artifact as real, before committing it, and before referencing the path in downstream prompts.
git-operation-serialization-preflight
Before any commit, stash, merge, reset, rebase, or checkout in a multi-agent or shared-checkout environment, run a bounded preflight to detect active git writers and stale index/config locks, then serialize the mutating step under a single-writer guarantee.
public-knowledge-graph-governance
Maintain public-safe knowledge graph artifacts for llm-wiki and similar markdown knowledge bases. Use when changing graph generators, validators, schema docs, weekly freshness checks, or public/private source-scope boundaries.
llm-wiki-weekly-freshness
Class-level governance workflow for keeping llm-wiki-style markdown knowledge bases current, public-safe, graph/index-valid, and useful for code development. Use when reviewing llm-wiki architecture/content, scanning new LLM concepts, maintaining public knowledge graphs, producing an issue roadmap, or running recurring freshness cadence.
llm-wiki-source-extraction-coverage
Doc-type-aware extraction contract for llm-wiki source ingestion with measurable coverage and source-anchored traceability. Use when (1) ingesting a PDF, DOCX, XLSX, PPTX, HTML, or scanned-image source into a wiki `sources/` page, (2) computing the pre-extraction estimate (what fraction of the source we expect to recover) and post-extraction yield (what fraction we actually recovered), (3) anchoring wiki claims back to specific page / paragraph / cell / slide positions in the source so a reviewer can re-verify or revise against the actual document, (4) deciding whether OCR fallback or manual transcription is needed. Codifies workspace-hub's existing OCR fallback chain and python-docx / openpyxl / trafilatura patterns into a format-specific routing table. Companion to research/llm-wiki-page-shape-contract (Rule 7 input-layer pages) and research/llm-wiki — this skill is the defense against silent extraction failure.