# pricing.as_of now declares what it measures, and market detail reports its own read time (https://docs.predictorsdk.com/changelog/2026-08-24-pricing-freshness-contract)

2026-08-24 · New, SDK

New as_of_kind and observed_at on GET /v1/markets/{market_id}, so a quote-freshness bound can be enforced on every provider instead of guessing which platforms publish a real quote timestamp.

`GET /v1/markets/{market_id}` now returns `pricing.as_of_kind` and `pricing.observed_at`. Both are additive; `pricing.as_of` is unchanged and existing consumers keep parsing as before.

The problem they solve is that `as_of` was the only quote timestamp on the response, and it does not mean the same thing on every platform. On Hyperliquid it is the order book's own server time and moves with the book. On Kalshi it is a record write that does not move at all while the market is quoted: across two live runs on 2026-08-24 it advanced on 0 of 39 and then 0 of 42 open markets — including five whose prices moved inside the window — and ran anywhere from 15 hours to 137 days old on markets reporting `status: open` with a live two-sided book. Four different meanings arrived in one RFC3339 string with nothing to tell them apart, so a consumer with a single code path had no good option: a 30-second bound rejected every Kalshi and Polymarket market, and loosening it enough to admit them silently accepted a badly stale Hyperliquid or SX Bet book.

`as_of_kind` names which meaning you received. `quote` — the stamp advances when the quote advances, so an age bound on it is meaningful (Hyperliquid, and SX Bet's V2 best-odds path). `record_refresh` — it advances on a periodic rewrite of the provider's record whether or not the quote moved, so it bounds record age in minutes and quote age not at all (Polymarket: it advanced on 60 of 60 and then 25 of 25 markets while only one of those prices changed, 45 to 405 seconds old). `record_static` — it does not advance while the market is quoted, so it bounds nothing at any threshold (Kalshi). `unknown` — `as_of` is null and the record carries no timestamp of any kind (Predict, AlphaArcade, and SX Bet from the 2026-08-25 V3 cutover, whose order book publishes an opaque monotonic `version` and no wall clock). The field is always present, and `unknown` whenever `as_of` is null — the two can never contradict each other.

One caveat on `quote`, because it is easy to over-read: it means the stamp tracks the quote, not that every `quote` provider supports the same threshold. Hyperliquid's `l2Book` time tracks wall clock to the second. SX Bet's marks when the resting top-of-book order was posted, so on a thin book it is legitimately old — 39 seconds to 2.5 hours measured, median around 24 minutes. Both are honest quote stamps; size the bound to the venue rather than applying one seconds-scale threshold everywhere.

`observed_at` is when PredictorSDK read the quotes. Unlike `as_of` its definition does not vary by platform, which makes it the field to bound when you want one threshold that behaves identically everywhere. It is named the way `trading_fees.observed_at` is, and for the same reason: `as_of` is the provider's own stamp, and reusing that name for a differently-defined value would bake the confusion into a second field. It bounds the age of the read, not of the quote — this route reads the venue live on every request and caches nothing, so a fresh `observed_at` next to a day-old `as_of` on a `record_static` provider is the honest description of what the venue served. It is stamped before the upstream call, so it is never newer than the moment the quotes were actually observed and `now − observed_at` never understates their age. It is `null` only when `availability` is `unavailable`; a `no_quotes` reading is a successful observation of an empty book and is stamped.

The per-provider staleness ranges above are published in the `as_of` reference description so a threshold can be picked from measured behaviour rather than guessed. They are observed behaviour, not a contract — a venue can change how it writes its records at any time. The Kalshi figure in particular is wide because `as_of` there tracks when the record was last written, which scales with how long-dated the market is: a same-day game market runs a day or two, while `CHINAUSGDP-30` was `status: open` and quoting 0.15 / 0.19 on a stamp from 2026-04-09. That is the whole argument for `record_static` — there is no threshold to pick.

One correction while we are here: the 2026-06-05 entry announcing the pricing tier described `as_of` as a "conservative oldest-side quote timestamp". The oldest-side part is accurate and still holds. Calling it a quote timestamp without a per-provider caveat was not, and `as_of_kind` is now the authoritative answer on any given response.