pmxt vs matchwire — Prediction Market API Comparison
A head-to-head on event mapping, venue coverage, data, docs and pricing. The pmxt column is taken from what pmxt.dev publishes, checked 2026-09-29.
Short answer
Pick matchwire for one mapped row per game across Polymarket International, Polymarket US, Kalshi and PredictFun, mapping only, with every venue's own market ID and the exact request that reads it. Pick pmxt for breadth: more venues, prices and history, an SDK, and hosted trading. Both are hosted APIs; the difference is scope, not quality.
Comparison table
| Point | matchwire | pmxt |
|---|---|---|
| Event mapping | One row per game, same-event ID on every listing; venue IDs kept native | Router returns clusters of the same or related market across venues, with relation types and confidence scores (pmxt.dev/docs) |
| Venues | Four: Polymarket International, Polymarket US, Kalshi, PredictFun | Fifteen, including Polymarket, Kalshi, Limitless, Smarkets, Myriad, Metaculus, Opinion and Hyperliquid (pmxt.dev) |
| Docs | One docs page, llms.txt and a copy-paste AI prompt | Full docs site at pmxt.dev/docs, plus its own llms.txt |
| MCP | Not live yet — use llms.txt with your agent | Yes, pmxt.dev/docs/mcp |
| What the rows carry | Mapping only: no prices or order books — read the venue through the listing's request | Unified schema with prices, order books, historical candles and SQL over raw tick history |
| SDK | Plain HTTP and SSE; nothing to install | Python and TypeScript SDK, MIT licensed, self-host option |
| Trading | None. Mapping layer, not a broker | Hosted trading with a non-custodial escrow |
| Pricing | From $99 per month, 14-day trial (pricing) | Free, $29.99 and $99.99 per month, personal use, enterprise on request |
| Migration path | Key swap, ID swap, verify | The same three steps in reverse |
Where matchwire wins
One shape for the join: a row per game keyed ev:<sport>:<team-a>:<team-b>:<YYYY-MM-DD>, with each venue's own market ID beside it and a ready-made request for it. No prices and no order books, so the data you serve is the venue's own, read from the venue.
Where pmxt may fit
pmxt covers more ground than matchwire does: fifteen venues, historical candle data, SQL over tick history, an SDK in two languages, and hosted trading. If you need any of those, its hosted API is the fit — matchwire is only the join.
Migration
Key swap, ID swap, verify. The base URL and the ID you key on change; the venue market IDs you already hold stay valid, because each listing carries them back to you.
# before
GET https://api.pmxt.dev/... key: pmxt_live_...
# after
GET https://api.matchwire.win/api/v1/rows?sport=nfl key: YOUR_KEY
# the row you key on gains a mapped id; venue ids stay native
"id": "ev:nfl:cleveland-browns:pittsburgh-steelers:2026-10-02"
"listings": [ { "venue": "kalshi", "marketId": "KXNFLGAME-26OCT02PITCLE", "request": {...} } ]FAQ
- Is matchwire a pmxt fork?
- No. Separate product.
- Migration effort?
- Two fields: the base URL and the ID field. Venue market IDs keep working, so the work is in the client, not the data.
- Venue gaps?
- matchwire carries Polymarket International, Polymarket US, Kalshi and PredictFun. pmxt publishes fifteen venues (checked 2026-09-29).
- Pricing?
- matchwire starts at $99 per month with a 14-day trial; see pricing. pmxt publishes Free, $29.99 and $99.99 per month tiers.