# Predict's exact Polymarket join runs live, and two coverage limits are stated (https://docs.predictorsdk.com/changelog/2026-10-10-predict-join-and-coverage-limits)

2026-10-10 · Fix

Predict markets are now placed in their Polymarket twin's event by the condition ID Predict declares, and the docs say plainly that an SX Bet event_id stops resolving after its game and that Predict's NBA games are not matched yet.

Predict declares which Polymarket market each of its sports markets mirrors, by condition ID. Matching now uses that to put a Predict market in the same event as its Polymarket twin, instead of relying on two parsed slugs agreeing; the join had been wired into a code path production never runs. Every Predict market already agreed with its twin when this shipped, so no event ID, submarket or source market changed.

Two limits are now written down where you read them. An SX Bet `event_id` resolves on `GET /v1/events/{event_id}` only while SX Bet lists the fixture's markets, which stops when the game ends. A matching row keeps that `event_id` through the day after, so for a game that has been played it answers `404` while the row's `market_id` still resolves on market detail (see [Which identifier goes where](https://docs.predictorsdk.com/concepts/events-and-markets#which-identifier-goes-where)). And Predict's NBA games, which the docs said it did not list, are listed under a market variant that matching does not read yet, so NBA events carry no Predict market (see [Sources](https://docs.predictorsdk.com/concepts/sources)).