# Market detail now reports each venue's trading fee model (https://docs.predictorsdk.com/changelog/2026-08-21-venue-trading-fees)

2026-08-21 · New, SDK

A normalized, provider-neutral trading_fees descriptor on GET /v1/markets/{market_id}, so cross-venue cost comparison stops requiring six private formulas.

`GET /v1/markets/{market_id}` now returns `trading_fees`: the fee the prediction market itself charges to trade that market, normalized across all six platforms. (Nothing here relates to PredictorSDK's own subscription pricing.) Normalized price alone cannot answer "which venue is cheaper", because every venue's fee is non-linear in price and none of them is expressible as a single basis-point rate — two venues quoting the identical ask can differ by more than 100 bps in true cost, and which one is cheaper can invert during the trading day.

Every published model reduces to a per-share fee times the traded share count, so one descriptor covers all of them: `taker.model` is `quadratic` (`rate × (price × (1 − price)) ^ exponent` — Kalshi, Polymarket, AlphaArcade), `min_price` (`rate × min(price, 1 − price)` — Predict), `notional` (a flat fraction of notional), or `none`. Both the `taker` and `maker` legs are always returned and you pick; PredictorSDK does not infer which side you will be. `rounding` carries the venue's published rule where it publishes one.

`trading_fees.availability` keeps the same honesty contract as `pricing.availability`, and it is on a separate axis from the fee value: `availability` says what is known, the legs say what is charged. `published` means the full parameter set is known; `partial` means fees may be charged but a parameter is missing upstream, so nothing is guessed; `account_specific` means rates exist but are set per trading account and need your own venue credentials (SX Bet, Hyperliquid); `unavailable` means our own bounded parameter fetch degraded. A fee-free market is `published` with `model: "none"` and `rate: 0` — an asserted zero, distinguishable from all three of those.

Two details worth reading before you wire this into a router. `charge_basis` tells you what the fee is assessed on: `fill` for most venues, but `settlement_profit` for SX Bet, which charges on the profit of a winning position at settlement rather than on entry notional — a different shape, not just a different rate. And `scheduled_change` carries the next published parameter change with its effective time: Kalshi currently runs its entire MLB family at a half-rate `fee_multiplier` with a per-event override restoring the full rate at first pitch, so the fee doubles on a game that is already trading.

Only Kalshi costs extra upstream work for this — its parameters live on the parent series plus any scheduled per-event override — and those hops are bounded and cached, degrading to `availability: "unavailable"` rather than failing the lookup. Every other platform reads its fee parameters off the same market record the lookup already fetches.