Prediction Market Event Mapping — Same Event, One ID
How matchwire maps the same event across Polymarket International, Polymarket US, Kalshi, and PredictFun into one ID, and where the review loop sits.
What a mapped event is
One ID joining the venue markets that describe the same event. Its format is ev:<sport>:<team-a>:<team-b>:<YYYY-MM-DD>, and each venue's own market ID is kept beside it.
Inputs and output ID
Venue markets go in, a shared ID comes out. A row carries id, sport, league, name, teams, start, status, listings, markets, notes and seq; each listing carries venue, marketId, type, side, tier, confidence and the ready-made request.
Review loop
Matching is tiered and only alias-resolved equality auto-binds. Unsure matches are held back for review and never served as a guess, and a game that stops matching a filter comes back as a tombstone instead of silently vanishing. Accuracy figures are not published yet.
How it differs
Mapping-first API with docs: GET /api/v1/rows, GET /api/v1/rows?since=SEQ, GET /api/v1/sports, GET /api/v1/status, GET /api/v1/push and GET /health. Use the AI prompt on the docs page to have a coding assistant wire it up.
Use it
Query through the Prediction Market API. The step-by-step guide is how to map prediction markets. Start at the quickstart.