Skip to content

Probable single-sided Price and Batch Prices endpoints not implemented — only midpoint/book are used #1609

Description

@realfishsam

Gap

Probable's spec defines a side-aware single-token price lookup (buy/sell price for a specific token_id) and a batch multi-token pricing endpoint, distinct from the midpoint/full-order-book data core already fetches. Neither is wired into core.

Core

  • core/src/exchanges/probable/api.ts:614-651GET /public/api/v1/price (price for a token_id + side BUY/SELL) and POST /public/api/v1/prices (batch prices for multiple tokens).
  • Core only ever calls getPublicApiV1Midpoint (single midpoint, used for internal enrichment) and getPublicApiV1Book (full order book) — confirmed via grep, no PublicApiV1Price/PublicApiV1Prices call sites exist anywhere in the probable directory.

TypeScript SDK

Missing — no corresponding method on the Probable class in sdks/typescript/pmxt/client.ts.

Python SDK

Missing — no corresponding method on the Probable class in sdks/python/pmxt/_exchanges.py.

Evidence

core/src/exchanges/probable/api.ts:614-651 defines both operations; grep -rn "PublicApiV1Price\b\|PublicApiV1Prices" core/src/exchanges/probable/ returns hits only in api.ts (the spec descriptor), none in fetcher.ts/index.ts.

Impact

Users cannot get a fast, side-aware best price for a single Probable outcome, or batch-fetch prices across multiple tokens in one call, through pmxt — they must fetch and derive this from the full order book or midpoint instead, which is less efficient and doesn't distinguish buy/sell sides the same way.


Found by automated Core-to-SDK surface coverage audit

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions