mcpField
M
matchwire.win — Mapped Prediction Markets (Kalshi, Polymarket, Predict.fun)

matchwire.win — Mapped Prediction Markets (Kalshi, Polymarket, Predict.fun)

Remote
matchwire.winFinance0Updated 4w ago

About matchwire.win — Mapped Prediction Markets (Kalshi, Polymarket, Predict.fun)

matchwire.win provides mapped prediction-market data for Node.js and Python, returning one row per game matched across Kalshi, Polymarket US and International, and Predict.fun. It maps markets but supplies no prices or order books, for developers reconciling markets across venues.

Key features

  1. 01Match game markets across four venues
  2. 02Map winners, totals, handicaps, and more
  3. 03Preserve each venue's market ID
  4. 04Provide match tier and confidence
  5. 05Support deltas and SSE streaming
  6. 06Offer Node.js and Python clients

Use cases

  1. 01Find markets for the same game across venues
  2. 02Filter mapped data by sport or venue
  3. 03Sync local data from change updates
  4. 04Use mappings to compare markets across venues

MCP support

A JSON-RPC 2.0 MCP endpoint exposes read-only tools for sports, mapped rows, individual games, and venue markets to AI agents. MCP and the HTTP API use the same API-key access controls.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://api.matchwire.win/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://api.matchwire.win/mcpAuth required

Tools

Details

From the project README
matchwire.win

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.

import { Matchwire } from 'matchwire.win';

const mw = new Matchwire({ apiKey: process.env.MATCHWIRE_API_KEY });

const { rows, seq } = await mw.rows({ sport: 'nfl', venue: ['kalshi', 'poly'] });
const game = rows.find((r) => r.listings.length > 1);
console.log(game.name, game.listings.map((l) => `${l.venue}:${l.marketId}`));
  • Zero dependencies. One src/ directory on the global fetch. Nothing installs alongside it.
  • Node.js 18+, ESM and CommonJS, hand-written TypeScript declarations.
  • Typed errors — a 429 is distinguishable from a 401 invalid_key in 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

npm install matchwire.win      # Node.js — zero dependencies
pip install matchwire.win      # Python 3.9+ — standard library only

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):

import { Matchwire } from 'matchwire.win';

const mw = new Matchwire({ apiKey: process.env.MATCHWIRE_API_KEY });

const status = await mw.status();
console.log(`${status.store.events} games, ${status.store.bound} bound listings`);

const { sports } = await mw.sports();
console.log(sports.slice(0, 5).map((s) => `${s.sport} ${s.events}`));

const { rows } = await mw.rows({ sport: 'nfl', limit: 3 });
for (const row of rows) {
  console.log(row.name, row.status, row.listings.map((l) => l.venue).join('+'));
}

The repository ships the same thing with formatting and error handling: node examples/quickstart.mjs.

API

MethodEndpointReturns
status()GET /api/v1/statusService and per-venue health, current seq, coverage counts
sports()GET /api/v1/sportsSports with game counts, plus group ids (esports, american-football, …)
rows(params)GET /api/v1/rowsOne row per game with its per-venue listings
row(id)MCP get_rowOne game by its mapped id
stream(params)GET /api/v1/pushThe same updates as Server-Sent Events
callTool(name, args)POST /mcpAny tool the MCP endpoint advertises
tools()POST /mcpThe tool list the endpoint advertises
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) · predictfun
  • type= winner · total · handicap · map_winner · score · event
  • status= scheduled · live · ended
  • sport= a sport name (baseball, not mlb) or a group id from sports()
// Everything that changed since the last call, plus tombstones for pruned games.
let seq = 0;
const first = await mw.rows({ sport: 'esports', limit: 5000 });
seq = first.seq;

const delta = await mw.rows({ since: seq });
console.log(delta.rows.length, 'changed', delta.tombstones?.length ?? 0, 'gone');

// Stream instead of polling.
for await (const frame of mw.stream({ since: seq })) {
  console.log(frame.event, frame.data.rows?.length);
  if (Date.now() - started > 10_000) break;   // or AbortController
}
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.

import { Matchwire } from 'matchwire.win';
const mw = new Matchwire({ apiKey: process.env.MATCHWIRE_API_KEY });

console.log((await mw.tools()).map((t) => t.name));
const row = await mw.row('ev:nfl:arizona-cardinals:denver-broncos:2026-10-25');
console.log(row.listings.map((l) => l.venue));

Plain text for coding assistants: matchwire.win/llms.txt · MCP reference: matchwire.win/docs/mcp/

Errors

import { MatchwireError } from 'matchwire.win';

try {
  await mw.rows({ sport: 'nope' });
} catch (error) {
  if (error.isRateLimited) await sleep(error.retryAfterMs);   // 429
  else if (error.isAuthError) /* key missing or revoked */ ;
  else if (error.isPlanError) /* outside the plan's sports/venues */ ;
  else throw error;
}

Documentation

Python

from matchwire import Matchwire

mw = Matchwire(api_key=os.environ["MATCHWIRE_API_KEY"])
rows = mw.rows(sport="nfl", venue=["kalshi", "poly"])["rows"]
print(rows[0]["name"], [l["venue"] for l in rows[0]["listings"]])

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.