Gap
LimitlessExchange exposes watchUserTransactions(callback) — a Limitless-specific WebSocket subscription that streams live on-chain transaction events for the authenticated user. The method is implemented in the Python SDK but is entirely absent from the TypeScript SDK.
Core
File: core/src/exchanges/limitless/index.ts line 495
async watchUserTransactions(callback: (data: any) => void): Promise<void>
Delegates to LimitlessWebSocket.watchUserTransactions (core/src/exchanges/limitless/websocket.ts line 226). A dedicated example ships at core/examples/api-reference/exchange-specific/limitless-watchUserTransactions.ts.
TypeScript SDK
Missing — sdks/typescript/pmxt/client.ts has no watchUserTransactions method. The Limitless subclass defined near line 2442 of that file is a constructor-only extension of Exchange with no additional methods. Searching the entire sdks/typescript/ tree for watchUserTransactions returns zero results.
Python SDK
Present — sdks/python/pmxt/client.py line 2192:
def watch_user_transactions(self, callback: Optional[Any] = None) -> Any
Calls the sidecar's /watchUserTransactions endpoint and is part of the Python SDK's public surface.
Evidence
grep -rn "watchUserTransactions" sdks/typescript/ returns zero results. grep -n "watch_user_transactions" sdks/python/pmxt/client.py returns line 2192. grep -n "watchUserTransactions" core/src/exchanges/limitless/index.ts returns line 495. The example file core/examples/api-reference/exchange-specific/limitless-watchUserTransactions.ts exists and documents the intended SDK usage pattern.
Impact
TypeScript SDK users building Limitless integrations cannot subscribe to live transaction feeds for the authenticated user. Trade confirmation flows, on-chain activity monitors, and event-driven settlement logic that need to react to transactions in real time must either use the Python SDK or bypass the SDK entirely. The Python SDK parity gap means TypeScript users have a materially reduced Limitless on-chain streaming experience compared to Python users.
Found by automated Core-to-SDK surface coverage audit
Gap
LimitlessExchangeexposeswatchUserTransactions(callback)— a Limitless-specific WebSocket subscription that streams live on-chain transaction events for the authenticated user. The method is implemented in the Python SDK but is entirely absent from the TypeScript SDK.Core
File:
core/src/exchanges/limitless/index.tsline 495Delegates to
LimitlessWebSocket.watchUserTransactions(core/src/exchanges/limitless/websocket.tsline 226). A dedicated example ships atcore/examples/api-reference/exchange-specific/limitless-watchUserTransactions.ts.TypeScript SDK
Missing —
sdks/typescript/pmxt/client.tshas nowatchUserTransactionsmethod. TheLimitlesssubclass defined near line 2442 of that file is a constructor-only extension ofExchangewith no additional methods. Searching the entiresdks/typescript/tree forwatchUserTransactionsreturns zero results.Python SDK
Present —
sdks/python/pmxt/client.pyline 2192:Calls the sidecar's
/watchUserTransactionsendpoint and is part of the Python SDK's public surface.Evidence
grep -rn "watchUserTransactions" sdks/typescript/returns zero results.grep -n "watch_user_transactions" sdks/python/pmxt/client.pyreturns line 2192.grep -n "watchUserTransactions" core/src/exchanges/limitless/index.tsreturns line 495. The example filecore/examples/api-reference/exchange-specific/limitless-watchUserTransactions.tsexists and documents the intended SDK usage pattern.Impact
TypeScript SDK users building Limitless integrations cannot subscribe to live transaction feeds for the authenticated user. Trade confirmation flows, on-chain activity monitors, and event-driven settlement logic that need to react to transactions in real time must either use the Python SDK or bypass the SDK entirely. The Python SDK parity gap means TypeScript users have a materially reduced Limitless on-chain streaming experience compared to Python users.
Found by automated Core-to-SDK surface coverage audit