pmxt Alternative — matchwire for Mapped Prediction Markets
A pmxt alternative with same-event mapping across Polymarket International, Polymarket US, Kalshi, and PredictFun, plus docs and MCP.
Why teams switch
Mapped IDs, docs-led onboarding, and MCP for agents. No invented pmxt deficiencies.
Feature deltas
Short list only. The full table lives on pmxt vs matchwire.
Deltaspmxt covers more venues and adds prices, history and trading; matchwire covers four venues as mapping only, one row per game, with a venue-native request on every listing. Both columns checked 2026-09-29.
Migration in three steps
- Swap the key.
- Swap the ID field.
- Verify the mapped events.
Snippet
# 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": {...} } ]What stays the same
Venue concepts carry over: markets, prices, and outcomes. Only the IDs and the client change.
DetailsYour venue calls keep working: each listing carries the venue's own market ID and the exact request that reads it, so the mapped ID is added beside what you already hold instead of replacing it.
FAQ
- Switch effort?
- Two fields in the client: the base URL and the ID you key on. The venue market IDs you already store stay valid.
- What changes in code?
- The client's base URL and the ID field. Row keys gain a mapped ID, and each listing adds the venue's own ID and the request that reads it.
- Do mapped IDs replace venue IDs?
- No. They are attached alongside, formatted
ev:<sport>:<team-a>:<team-b>:<YYYY-MM-DD>. - Trial path?
- Start at the quickstart.