SDK drift: `Router.fetch_market_matches` calls server endpoint `"fetchMatches"` in Python but `"fetchMarketMatches"` in TypeScript

[realfishsam]

SDK Drift Report

Category: Method behaviour drift (wrong server endpoint)

TypeScript location: sdks/typescript/pmxt/router.ts line 255 — calls 'fetchMarketMatches'

Python location: sdks/python/pmxt/router.py line 201 — calls "fetchMatches" (stale endpoint name)

---

What the drift is

The TypeScript Router.fetchMarketMatches dispatches to the correct sidecar endpoint:

// sdks/typescript/pmxt/router.ts line 255
return this.callMethod('fetchMarketMatches', params);

The Python Router.fetch_market_matches dispatches to a different, apparently stale endpoint name:

# sdks/python/pmxt/router.py line 201
return await self._call_method("fetchMatches", params)

"fetchMatches" was the old name before the endpoint was renamed to "fetchMarketMatches". The Python router was not updated.

---

Why it matters

Python callers invoking router.fetch_market_matches(...) will hit the wrong (or non-existent) server endpoint, receiving either an error or stale/incorrect results while the TypeScript counterpart works correctly.

---

Expected behaviour

Router.fetch_market_matches in Python should call "fetchMarketMatches" to match the TypeScript implementation.