Event and market price monitoring
Polymarketエンドポイントを使えば、「Event and market price monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Collect Polymarket event and market detail, token prices, order books, midpoints, spreads, price history, tags, sports, leaderboards, and trade activity as normalized JSON for dashboards, research, and agent-native workflows. Not investment advice or real-time trading data.
Extract Polymarket events, markets, prices, order books, tags, leaderboards, and activity as structured JSON from credential-free public Gamma and CLOB data.
エンドポイントファミリー
6
ドキュメント化されたパラメータ
245
サンプル数
65
ライブカタログスナップショット
稼働エンドポイント
65
メソッド
GET, POST
必須パラメータ
109
スキーマ参照
65
{
"platform": "Polymarket",
"endpoint": "polymarket-search",
"method": "GET",
"path": "/polymarket/search",
"auth": "apiKey"
}ユースケース
Extract Polymarket events, markets, prices, order books, tags, leaderboards, and activity as structured JSON from credential-free public Gamma and CLOB data.
Polymarketエンドポイントを使えば、「Event and market price monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Polymarketエンドポイントを使えば、「Order book and liquidity research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Polymarketエンドポイントを使えば、「Tag, sport, and leaderboard tracking」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のPolymarketエンドポイントカタログから取得しています（エンドポイント65件、ドキュメント化されたリクエストパラメータ245個、公開レスポンススキーマ65件）。DocsとPlaygroundが参照しているカタログと同じものです。
Polymarketのエンドポイントは65件、25つのリクエストファミリーに分類されています（Market、Sports、Tagほか22件）。
これらのPolymarketエンドポイントには245個のリクエストパラメータがドキュメント化されており、うち109個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
65件のPolymarketエンドポイントのうち65件が実際のサンプルレスポンスを、65件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Polymarketのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、429、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Polymarketのエンドポイントは30個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
/polymarket/market/{id}
/polymarket/sports
/polymarket/tag/{id}
/polymarket/teams
/polymarket/token/{token_id}/price
/polymarket/event/{slug}
主要エンドポイント
/polymarket/searchSearches Polymarket and returns event results. The `status` enum accepts `open`, `closed`, and `all`; the `sort` enum accepts `relevance`, `volume24hr`, `volume`, `liquidity`, and `endDate`.
レスポンスに関する注記
- Empty valid searches return an empty `events` array. - `events[].markets` contains the nested markets returned by Polymarket for each event. - Invalid `status` or `sort` values return an invalid-parameter error before upstream IO.
MCPツール polymarket_search
/polymarket/eventsLists Polymarket events with their markets. Sort by 24-hour volume, total volume, liquidity, end date and more, filter to open or closed events, and page with `limit` (default 25, max 100) and `offset`. Each event has its slug, description, end date, liquidity, open interest and comment count; each market has its question, outcomes, best bid and ask, last trade price and volume.
レスポンスに関する注記
- Invalid enum or identifier values return invalid-parameter errors before upstream IO. - This endpoint is not investment advice or real-time trading data.
MCPツール polymarket_events
/polymarket/event/{slug}Returns one Polymarket event. This endpoint does not require a Polymarket user token, wallet signature, cookies, or personal account authentication.
レスポンスに関する注記
- Returns one event. - This is a public read-only endpoint and does not require a Polymarket user token, wallet signature, cookies, or personal account authentication. - Nested markets use the same `MarketSummary` shape as Polymarket list endpoints.
MCPツール polymarket_event_detail
/polymarket/marketsLists Polymarket markets, up to `limit` rows (default 25, max 100), starting at `offset` (default 0, max 10000). Sort with `order`, such as `volume24hr` or `liquidity`, flip direction with `ascending`, and filter with `closed`. Each market has its question, slug, prices, volume, liquidity, token ids and outcomes.
レスポンスに関する注記
- Invalid enum or identifier values return invalid-parameter errors before upstream IO. - This endpoint is not investment advice or real-time trading data.
MCPツール polymarket_markets
/polymarket/market/{id}Returns one Polymarket market. This endpoint does not require a Polymarket user token, wallet signature, cookies, or personal account authentication.
レスポンスに関する注記
- Returns one market. - This is a public read-only endpoint and does not require a Polymarket user token, wallet signature, cookies, or personal account authentication. - Outcome prices, liquidity, volume, best bid, best ask, and last trade price are returned as numeric fields when values are available.
MCPツール polymarket_market_detail
/polymarket/token/{token_id}/priceReturns the current price for one Polymarket outcome token, identified by the required `token_id`. `side` is `buy` or `sell` and defaults to `buy`. The response gives the `price` as a number, the `side` used and a `fetched_at` time. It is a snapshot, not trading advice.
レスポンスに関する注記
- Returns the public CLOB buy or sell price for one token id. - This is a read-only public CLOB snapshot and is not investment advice or trading instruction.
MCPツール polymarket_token_price
関連API
Prediction Markets
Collect Kalshi events, markets, series, recent trades, order books, exchange schedule, and historical market candlesticks as normalized JSON for dashboards and research. Not investment advice or real-time trading data.
Prediction Markets
Collect Metaculus questions, community forecasts and forecast history, question metadata, options, and comment feeds as normalized JSON for research and tracking. Not investment, forecasting, or decision advice.
Prediction Markets
Read the public navigation and reference material from DraftKings Predictions without confusing it for a market feed. The endpoints return category links, settlement-source references, and a region/status map; they do not return quotes, trades, balances, or trade-slip state.
Polymarketのスクレイピング方法
Polymarket's prediction-market data is spread across several public services — events and markets, the CLOB order book, price history, and trade activity — each with its own identifiers and shapes. Crawlora's 65 Polymarket endpoints put all of it behind one key as normalized JSON. Research data, not investment advice or a trading connection. A pull on 2026-10-27 showed events and markets both ordered by 24-hour volume at 25 rows per call, led by the Ballon d'Or Winner 2026 event.
Search events by free-text q with status and sort filters, or list events and markets ordered by 24-hour volume, total volume, liquidity, or end date.
Event detail takes a slug, with a by-id variant; market detail takes an id; the CLOB market endpoint takes a condition_id.
Per-token endpoints return price by buy or sell side, midpoint, spread, and the full order book — each with a batch variant for when you need many tokens at once.
Token price history takes an interval from 1m through max, and the activity, leaderboard, and trade endpoints cover who traded what, filtered by size band.
events returned limit 25, offset 0 and order volume24hr, so the default is not alphabetical or by close date. The first event was Ballon d'Or Winner 2026 (slug ballon-dor-winner-2026), fetched 2026-10-27 06:00 UTC.
markets returned 25 rows with a numeric id, a slug and a 0x condition_id; the first asked whether there will be no change in Fed interest rates. The CLOB routes take condition_id, so store both.
tags returned 25 tags (the first labelled 01.xyz, id 103223), which you can page with limit and offset.
エージェントスキル
Crawlora のエージェントスキルをインストールすると、スクレイパーを書かずに、ドキュメント化された API 経由で Polymarket のデータを JSON として取得できます。Polymarket に対応するスキル:
Compare public event forecasts across Crawlora Polymarket, Kalshi, and Metaculus tools. Use for a matched-question consensus brief or dated forecast…
npx skills add github.com/Crawlora-org/crawlora-skills --skill forecast-consensus-comparisonResearch prediction-market odds, order books, price history, and public market-rule context from Polymarket, Kalshi, Metaculus, and DraftKings…
npx skills add github.com/Crawlora-org/crawlora-skills --skill prediction-markets-researchFAQ
Polymarket exposes several public credential-free services rather than one documented developer API, and they use different identifiers and response shapes. Crawlora's endpoints wrap them behind a single key and a consistent format so you are not integrating four services separately.
No. These endpoints are read-only market data for dashboards and research. Crawlora places no orders, is not a broker or an investment adviser, and nothing here is investment advice or a real-time trading feed.
Prices, midpoints, spreads, and order books are addressed by token_id, which comes back in the market or event detail response. Batch endpoints take several token ids in one call when you are tracking a whole market.
Token price history takes an interval of 1m, 1h, 6h, 1d, 1w, all, or max, with fidelity and explicit start and end timestamps for narrower windows.
By 24-hour volume, as order volume24hr showed on 2026-10-27.