Read live odds across every prediction venue at once
Prediction-market odds and resolution data across Polymarket, Kalshi and more on one endpoint. Billed per call in USDC, with no venue accounts to maintain.
Prediction market API: Polymarket, Kalshi and more, read from one endpoint
Market and event lists, trades, orderbook snapshots, candlesticks, volume and open-interest history and positions for Polymarket and Kalshi; market lists and orderbook history for Limitless, Opinion and Predict.Fun; a cross-venue search that matches the same event across all of them; and UMA oracle state for Polymarket resolutions. Wallet analytics — leaderboards, per-wallet P&L and positions, smart-money positioning, identity and cluster lookups — sit on the same prefix.
Every endpoint is one request billed at a flat per-call rate whichever tier it belongs to. List endpoints paginate by offset or by keyset cursor, and the table below shows the query parameters the markets list accepts. Path parameters such as a condition id come from the list endpoints.
How to call the prediction market data API — markets, events, trades, orderbooks
One endpoint, priced in dollars before it runs and settled in USDC. No API key and no account — the request pays for itself.
GET /api/v1/pm/polymarket/markets
Host: blockrun.aiRequest parameters
| field | type |
|---|---|
| status | string |
| min_price | number |
| max_price | number |
| min_open_interest | number |
| min_volume | number |
| tags | string |
| event_slug | string |
| search | string |
| condition_id | string |
| question_id | string |
| market_id | string |
| market_slug | string |
| token_id | string |
| predexon_id | string |
| end_after | integer |
| end_before | integer |
| sort | string |
| limit | integer |
| pagination_key | string |
| offset | integer |
| min_volume_1d | number |
| min_volume_7d | number |
| min_volume_30d | number |
| min_trades_1d | integer |
| min_trades_7d | integer |
| min_trades_30d | integer |
What it covers
Prediction market API pricing per call, by tier
Prediction market data for trading agents: from an MCP host or the SDK
In Claude Code, Claude Desktop, Cursor, Windsurf, Cline and any other MCP host, this is the blockrun_markets tool of the BlockRun MCP server — the agent calls it like any other tool and the result comes back in the conversation. In OpenClaw, Codex and Hermes, ClawRouter exposes the same catalog. In your own code, the Python and TypeScript SDKs wrap the endpoint above with types; any HTTP client works too. Every harness, with its setup →
No account and no API key stand between an agent and the first call: the request is quoted in dollars and the agent's client pays it. A team that prefers keys gets one, with a monthly invoice.
Prediction market API vs the Polymarket and Kalshi APIs and Dune dashboards
Polymarket and Kalshi each publish an API for their own venue, and each is the right source for placing an order there. Reading across them is the problem: the same event is listed under different names, in different units, with different resolution rules, and the smaller venues — Limitless, Opinion, Predict.Fun — have thinner APIs still. Analysts fall back to Dune dashboards, which are hours old and not callable from an agent.
This endpoint reads every venue on the card through one shape, and adds what no single venue can: a cross-venue search that matches the same event across all of them, wallet analytics (leaderboards, per-wallet positions and P&L, smart-money positioning), and UMA oracle state for Polymarket resolutions. Every request is a flat per-call price by tier, quoted before it runs.
It is data, not trading. It reads odds, orderbooks, trades and resolutions; it does not place positions. An agent that wants to trade reads here and orders at the venue.
Related tools
Prediction market API questions: venues, odds, wallets, resolution, pricing
Which prediction market venues does the API cover?
Polymarket and Kalshi in depth — markets, events, trades, orderbooks, candlesticks, positions — plus Limitless, Opinion and Predict.Fun, with a cross-venue search that lines the same event up across all of them.
Can I get live Polymarket odds through the API?
Yes. Market prices, orderbook snapshots and recent trades are read live from the venue at request time, not served from a daily snapshot.
Does the prediction market API support Kalshi as well as Polymarket?
Yes. Kalshi markets, events, trades, orderbooks and history are on the same path prefix with the same shape, and the cross-venue search matches Kalshi and Polymarket listings of the same event.
How is the prediction market data API priced?
Per call, in USDC, at a flat rate by tier — a market list and an orderbook snapshot each cost one call — with no venue account or key. The rate card above carries every endpoint.
How do I know how a Polymarket market resolved?
UMA oracle state for Polymarket resolutions is exposed on its own endpoint, alongside each market's resolution data.
Is this a prediction market trading API?
No — data only. It reads odds, markets, trades and resolutions and does not place positions. An agent that trades reads here and orders at the venue.
Prediction market API vs the Polymarket API, Kalshi API or Dune?
Each venue's API covers that venue alone; Dune dashboards are hours old and not callable. This reads every venue through one shape, matches events across them, and is priced per call for an agent to hit at request time.
Can I track whale or smart-money wallets on Polymarket?
Yes. Wallet analytics on the same prefix cover leaderboards, per-wallet positions and P&L, smart-money positioning, and identity and cluster lookups for an address.
Can an AI trading agent call the prediction market API without an account?
Yes. Each request pays for itself, so an agent reads odds across every venue from its own balance with no venue accounts to maintain.
Two ways to run this
Get an API key
Sign in, get a key, and call the same endpoints with usage billed to your account. For teams that want one invoice instead of one wallet.
Get an API keyOr let your agent pay per call, in USDC
No account, no API key. Three steps, and the last one is the request this page is about.
- Point your agent at BlockRun
Install ClawRouter, or add the BlockRun MCP server to Claude Code, Cursor, Codex or OpenClaw. Any OpenAI-compatible client works too — change the base URL, nothing else.
curl -fsSL https://blockrun.ai/ClawRouter-update | bash - Fund a wallet with USDC
Send USDC to a wallet on Base or Solana. There is no account to create and no API key to issue: the wallet is the account, and it pays per call.
- Call Prediction Market API
The first call returns HTTP 402 with the exact price, your agent signs it, and the answer comes back. Payment settles on-chain; nothing is charged if the call fails.
GET /api/v1/pm/polymarket/markets Host: blockrun.ai
Explore everything on BlockRun
- GPT-6 Astra
- GPT-6.1 Sol
- GPT-6 Sol
- GPT-6 Luna
- GPT-5.6 Sol
- GPT-5.6 Terra
- GPT-5.6 Luna
- GPT-5.6 Sol Pro
- GPT-5.6 Terra Pro
- GPT-5.6 Luna Pro
- GPT-5.5
- GPT-5.5 Pro
- ChatGPT Instant (GPT-5.5)
- GPT-5.4
- GPT-5.4 Pro
- GPT-5.1
- GPT-5.2
- GPT-5.4 Mini
- GPT-5 Mini
- GPT-5.4 Nano
- GPT-5.2 Pro
- GPT-5.3 Codex
- GPT-4.1
- GPT-4.1 Mini
- GPT-4.1 Nano
- GPT-4o
- GPT-4o Mini
- o1
- o3
- o3-mini
- All models →