Prediction Market Spread Finder: Kalshi vs Polymarket
Pricing
from $0.70 / 1,000 markets
Prediction Market Spread Finder: Kalshi vs Polymarket
Kalshi and Polymarket odds in one table: yes/no price, implied probability, volume, liquidity and close time per market, with the same question matched across both venues and the price spread between them. No login, no API key.
Pricing
from $0.70 / 1,000 markets
Rating
0.0
(0)
Developer
Detroit Web Agent - Open Data
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
12 days ago
Last modified
Categories
Features
Share
Prediction Market Spread Finder: Kalshi vs Polymarket odds in one table
Use this to pull live odds from Kalshi and Polymarket into one dataset, match the same question across both venues, and see where they disagree.
One clean row per market, from both venues' public APIs, with the cross-venue spread already computed. Kalshi and Polymarket often list the same question (a Fed decision, a CPI print, an election, a bitcoin price level) with different wording, different units and different prices. This actor reads both, normalizes each market to a common topic, pairs markets that ask the same thing (same subject, same month and year, same strike, same direction), and adds the counterpart's price, the spread between venues and a crossVenueEdge computed from the best asks.
- What you get: venue, market id, title, outcome, yes and no price, implied probability, best bid and ask, last price, volume, 24h volume, liquidity, open interest (Kalshi), close time, category, a normalized
topic, the matched market on the other venue,spread,crossVenueEdge, market URL and fetch time. - Who it is for: traders and quants comparing venues, research and newsroom desks that chart implied probabilities, data teams that track odds over time, and builders of dashboards, bots and AI agents that need prediction market prices as clean JSON.
- Price: $1.00 per 1,000 market rows ($0.001 each) plus $0.00005 per run start. Filtered, invalid or unpriced markets are never charged.
- No login, no API key: both venues publish these prices through public, keyless APIs.
How it works: what this prediction market spread finder does
- Reads Kalshi through the official Trade API v2: open events and their markets, with order-book bid and ask in dollars, volume and open interest.
- Reads Polymarket through the public gamma API (events, markets, outcomes, volume, liquidity) and refreshes prices from the public CLOB order book (best bid and best ask per outcome token).
- Normalizes every market to a
topic. Wording is folded to one vocabulary: "hike", "raise" and "increase" becomeincrease; "25 bps" and "25bps" become25bps; ">25bps" and "50+ bps" become50plusbps; "$100,000" becomes100000usd; "at least" and "≥" becomeabove. - Matches the same question across venues. A pair needs a text similarity of 0.62 or more and the same years, months, numeric strikes and direction words, and close times that agree. Each market is paired at most once (mutual best match), so one Kalshi market never claims three Polymarket markets.
- Orders the output usefully: matched pairs first (both rows next to each other, largest combined volume first), then the remaining markets alternating venues by volume.
Use cases
- Cross-venue price checks: a trader pulls every Fed, CPI and jobs-report market each morning with
onlyMatchedon and sorts byspreadto see where Kalshi and Polymarket disagree by more than a few points. - Research and journalism: a newsroom pulls implied probabilities for a topic (recession, a candidate, a bitcoin price level) from both venues into one sheet for a chart or a story, with the source link on every row.
- Odds history: a data team schedules the actor every hour and appends rows to a warehouse to track how the price of the same question moves on each venue over time, keyed by
topicormatchGroupId. - Bots and AI agents: an agent calls the actor through the Apify API or MCP server to answer "what do prediction markets say about X" with prices from both venues instead of one.
Input
| Field | Type | Default | What it does |
|---|---|---|---|
keyword | string | fed (prefill) | Words that must appear in the market or event title, for example fed, bitcoin, cpi, election. Empty = top markets of the chosen categories. |
categories | list | Politics, Elections, Economics, Finance, Crypto | Normalized categories: politics, elections, economics, finance, crypto, sports, tech, science, culture, weather, world, health. |
sources | list | both | kalshi, polymarket, or both. Matching needs both. |
status | string | open | Only open, tradable markets are tracked. |
minVolume | integer | 0 | Skip markets with lower lifetime volume. |
closesWithinDays | integer | empty | Only markets that close within this many days. |
maxItems | integer | 25 | Stop after this many rows (max 2,000). |
matchAcrossVenues | boolean | true | Pair the same question across venues and add spread fields. |
onlyMatched | boolean | false | Return only markets that have a counterpart. |
minAbsSpread | number | 0 | Only matched markets whose yes prices differ by at least this much (0.03 = 3 points). |
refreshPolymarketPrices | boolean | true | Use live CLOB bid and ask for Polymarket instead of the cached gamma price. |
Example input
{"keyword": "fed","maxItems": 30,"onlyMatched": false}
Output
One row per market, 36 flat fields. Main fields:
| Field | Meaning |
|---|---|
source | kalshi or polymarket |
marketId, eventId | Kalshi ticker / Polymarket id |
title, eventTitle, outcome | The question, its parent event and the outcome yesPrice refers to |
yesPrice, noPrice, impliedProbability | 0-1. Order-book mid when both sides quote, otherwise last trade |
yesBid, yesAsk, noBid, noAsk, lastPrice | Top of book and last trade, 0-1 |
volume, volume24h, volumeUnit | Kalshi: contracts ($1 face value each). Polymarket: USDC |
liquidity, liquidityBasis | Polymarket: reported liquidity in USDC. Kalshi: dollars resting at the top of the book |
openInterest | Kalshi open interest in contracts |
closeTime | Scheduled close, ISO 8601 UTC |
category, topic | Normalized category and the cross-venue topic key |
matchGroupId, matchedSource, matchedMarketId, matchedTitle, matchedUrl, matchedYesPrice, matchScore | The counterpart on the other venue |
spread | yesPrice - matchedYesPrice (positive = this venue prices yes higher) |
crossVenueEdge | 1 - min(yesAsk here + noAsk there, noAsk here + yesAsk there), before fees |
url, priceSource, fetchedAt | Market link, where the price came from, when the row was read |
Sample output
Real rows from our test data (keyword fed, read 2026-11-05):
| Venue | Market | Yes | Spread | Topic |
|---|---|---|---|---|
| Kalshi | Will the Federal Reserve Hike rates by 25bps at their December 2026 meeting? | 0.645 | +0.010 | fed increase 25bps december 2026 |
| Polymarket | Will the Fed increase interest rates by 25 bps after the December 2026 meeting? | 0.635 | -0.010 | fed increase 25bps december 2026 |
| Kalshi | Will the Federal Reserve Hike rates by 0bps at their December 2026 meeting? | 0.330 | -0.005 | fed nochange december 2026 |
| Polymarket | Will there be no change in Fed interest rates after the December 2026 meeting? | 0.335 | +0.005 | fed nochange december 2026 |
| Kalshi | Will the Federal Reserve Hike rates by 25bps at their January 2027 meeting? | 0.205 | +0.030 | fed increase 25bps january 2027 |
| Polymarket | Will the Fed increase interest rates by 25 bps after the January 2027 meeting? | 0.175 | -0.030 | fed increase 25bps january 2027 |
One row as JSON (shortened):
{"source": "kalshi","marketId": "KXFEDDECISION-26DEC-H25","title": "Will the Federal Reserve Hike rates by 25bps at their December 2026 meeting?","yesPrice": 0.645,"impliedProbability": 0.645,"volumeUnit": "contracts ($1 face value each)","closeTime": "2026-12-09T18:59:00Z","topic": "fed increase 25bps december 2026","matchedSource": "polymarket","matchedYesPrice": 0.635,"spread": 0.01,"url": "https://kalshi.com/markets/kxfeddecision","priceSource": "kalshi_orderbook","fetchedAt": "2026-11-05T18:00:00.000Z"}
Pricing
Pay per event, no monthly rental:
| Event | Price | When |
|---|---|---|
market-row | $0.001 ($1.00 per 1,000) | Each market row written to your dataset |
apify-actor-start | $0.00005 | Once per run |
Worked example: the example input (fed, 30 rows) costs 30 x $0.001 + $0.00005 = $0.03005. An hourly check of 50 matched markets costs about $0.05 per run, about $1.20 per day. A run can never cost more than $0.00005 + maxItems x $0.001, and the actor stops cleanly at your "Maximum cost per run" setting. A run that finds nothing costs only the start event.
How to run it
- Apify Console: set a keyword or a category, press Start, and open the Markets table, or export JSON, CSV or Excel.
- API and clients: call
transparent_meteorite/prediction-market-spread-finderfrom the Apify REST API or the JavaScript and Python clients. - Schedules, webhooks, n8n, Make, Zapier and AI agents: every row has a stable
marketId, afetchedAtdate and numeric prices, so it drops into a sheet, a database or a workflow without reshaping.
Limitations
- Text matching, not resolution matching. Two markets with the same topic can still resolve on different sources or rules. Read both venues' rules before treating a spread or
crossVenueEdgeas tradable. Edge is computed from best asks and is before fees, slippage and position limits. - Best on economics, politics and crypto price levels, where questions share dates, strikes and direction. Sports markets are listed but team-name aliases are not resolved, so fewer sports markets pair up.
- Units differ by venue: Kalshi volume is in contracts and Kalshi liquidity is the top of the book only; Polymarket reports USDC.
- Open markets only. No order-book depth beyond the best bid and ask, no trade history, no account data.
- Kalshi links open the market's series page on kalshi.com. Very broad keywords scan Kalshi's open events within a time budget; a category or a narrower keyword returns faster.
Data source and license
Prices come from Kalshi's public Trade API v2 and Polymarket's public gamma and CLOB APIs, which both venues publish for read access without an account. The actor only reads public market data. It does not trade, place orders or log in.
Related actors
- SEC EDGAR Filings Monitor: new SEC filings by company or form type, for event-driven research next to market odds.
- Federal Register Rules and Notices Monitor: new US federal rules and notices, useful for policy and regulation markets.
- DeFi Protocol TVL and Yields Monitor: on-chain protocol TVL and yields, for crypto research alongside crypto price markets.
Use with the API, n8n, Make, Zapier or AI agents
API (one call, returns the rows as JSON):
curl -X POST "https://api.apify.com/v2/acts/transparent_meteorite~prediction-market-spread-finder/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \-H "Content-Type: application/json" \-d '{"keyword":"fed","maxItems":30}'
The call waits up to 5 minutes. For bigger inputs, start the run with /runs instead and read the dataset when it finishes.
Python
from apify_client import ApifyClientclient = ApifyClient("YOUR_APIFY_TOKEN")run = client.actor("transparent_meteorite/prediction-market-spread-finder").call(run_input={"keyword": "fed", "maxItems": 30})for row in client.dataset(run["defaultDatasetId"]).iterate_items():print(row)
- n8n, Make, Zapier: use the Apify app's "Run Actor" step with actor
transparent_meteorite/prediction-market-spread-finder, paste the input JSON, then map the dataset items to your sheet or CRM. - Clay: add an HTTP API column that calls the run-sync endpoint above.
- Schedules: in Apify Console, Schedules, run it daily or weekly with the same input for a steady feed.
- AI agents (MCP): connect the Apify MCP server at
https://mcp.apify.com?tools=transparent_meteorite/prediction-market-spread-finderto Claude, Cursor or any MCP client, and your agent can run Prediction Market Spread Finder on request.
FAQ
Do I need a Kalshi or Polymarket account or API key? No. Both venues publish these prices through public, keyless APIs. You only need an Apify account.
How does it decide two markets are the same question?
Each title is folded to a normalized topic (subject, direction, strike, month, year). A pair needs a similarity of 0.62 or more, identical strikes, direction and dates, and close times that agree. matchScore shows the similarity on every pair.
What is the difference between spread and crossVenueEdge?
spread compares mid prices (yes here minus yes there). crossVenueEdge uses the asks you would actually pay: buying yes on one venue and no on the other. A positive edge means the two asks sum to less than $1 before fees.
Why is Kalshi volume so much larger than Polymarket volume on the same market?
Kalshi counts contracts with $1 face value; Polymarket counts USDC traded. Use volumeUnit before comparing them.
Can I get only one venue?
Yes. Set sources to ["kalshi"] or ["polymarket"]. Matching and spread fields are then empty.
How fresh are the prices?
Prices are read at run time. Polymarket prices are refreshed from the CLOB order book by default, and every row carries fetchedAt.
How much does a typical run cost? $0.001 per market row. 30 rows cost about $0.03, 1,000 rows about $1.00.