
matchwire.win — Mapped Prediction Markets (Kalshi, Polymarket, Predict.fun)
win.matchwirev0.1.0Updated Sep 30, 2026
One row per game, matched across Kalshi, Polymarket US/Intl and Predict.fun. Mapping only.
Overview
Lets an assistant look up prediction-market games mapped across Kalshi, Polymarket US/International and Predict.fun, returning one row per game with each…
- What it does
- Exposes read-only tools over a remote MCP endpoint: list_sports, find_rows, get_row, get_venue_market, report_issue and service_status. Results give one row per game with per-venue listings, each carrying the venue's own market id, a match tier (exact, normalized, fuzzy), a confidence value and the request that reads that market from the venue. Market types such as winners, spreads, totals and props are matched, and the line is part of the match. Deltas and SSE streaming are available through the HTTP API.
- When to use it
- Useful when an assistant needs to identify which market on one prediction venue corresponds to the same game on another, for example to compare a Kalshi market with its Polymarket counterpart. It is a mapping layer only, so prices and order books still have to be read from each venue with a source you already have.
- Requirements
- Remote streamable HTTP endpoint at no local runtime needed. Requires an x-api-key header holding a matchwire.win API key (mw_...), issued from the provider's pricing page; plans start at $99/month with a 14-day trial on Starter. Results are narrowed to the key's plan.
Installation
In SourceWeft
- Open matchwire.win — Mapped Prediction Markets (Kalshi, Polymarket, Predict.fun) in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"mapping": {
"type": "http",
"url": "https://api.matchwire.win/mcp"
}
}
}README
matchwire.win
Mapped prediction-market data for Node.js and Python. One client, no dependencies: matchwire.win returns one row per game, matched across Kalshi, Polymarket US, Polymarket International and Predict.fun, with each venue's own market id left intact — the pieces you need to compare a Kalshi API market with its Polymarket API twin without owning a reconciliation job.
Market types are matched too: winners, spreads and handicaps, totals and props. The line is part of the match, so over 45.5 is never confused with over 48.5.
Mapping only — no prices, no order books. Prices come from each venue; this library tells you which market on which venue is the same game.
- Zero dependencies. One
src/directory on the globalfetch. Nothing installs alongside it. - Node.js 18+, ESM and CommonJS, hand-written TypeScript declarations.
- Typed errors — a
429is distinguishable from a401 invalid_keyin code, not by string matching. - Deltas and streaming —
since=<seq>for changed rows and tombstones, or the same updates over SSE. - MCP included — the same tools an AI agent gets from
https://api.matchwire.win/mcp. - MIT licensed.
Install
Get a key at matchwire.win — plans start at $99/month with a 14-day trial on Starter.
Quickstart
Save as quickstart.mjs and run node quickstart.mjs (Needs MATCHWIRE_API_KEY in the environment):
The repository ships the same thing with formatting and error handling: node examples/quickstart.mjs.
API
Filters
sport, venue, type, league, status accept a value or a comma list; they combine. since=<seq> switches to a delta (changed rows plus tombstones).
venue=kalshi·poly(Polymarket US) ·polyintl(Polymarket International) ·predictfuntype=winner·total·handicap·map_winner·score·eventstatus=scheduled·live·endedsport=a sport name (baseball, notmlb) or a group id fromsports()
Mapping, not prices
Every listing carries the venue's own marketId, a tier (exact, normalized, fuzzy) and a confidence, plus the exact request that reads that market from the venue. Use the mapped row to decide what to compare, then read the prices from each venue with the source you already have.
Agents and MCP
POST https://api.matchwire.win/mcp speaks JSON-RPC 2.0 with your key in the same x-api-key header. Tools: list_sports, find_rows, get_row, get_venue_market, report_issue, service_status. Read-only; every tool result is narrowed by your key's plan exactly like the HTTP API.
Plain text for coding assistants: matchwire.win/llms.txt · MCP reference: matchwire.win/docs/mcp/
Errors
Documentation
- Docs — https://matchwire.win/docs/
- Event mapping, explained — https://matchwire.win/how-to-map-prediction-markets/
- Kalshi API, mapped — https://matchwire.win/kalshi-api/
- Polymarket API, mapped — https://matchwire.win/polymarket-api/
- Prediction Market API — https://matchwire.win/prediction-market-api/
- Plans — https://matchwire.win/#pricing
Python
See python/README.md. Standard library only, Python 3.9+.
License
MIT. Not affiliated with Kalshi, Polymarket or Predict.fun; venue names are used to say what is mapped.
Source: README.md at commit f4a56fb
Tools
0Version history
1- v0.1.0LatestSep 30, 2026
