# The catalog's freshness stamp now marks when the crawl started (https://docs.predictorsdk.com/changelog/2026-10-11-catalog-freshness-start)

2026-10-11 · Fix

snapshot.observed_at on GET /v1/markets is when the oldest provider crawl began, not when its snapshot was published, so no row on the page is older than it.

`snapshot.observed_at` on `GET /v1/markets` is now the moment the oldest provider's crawl began. Until now it was the moment that crawl's snapshot was published, which comes after the crawl has read every row. A crawl takes time: Kalshi's, the longest, takes about 45 seconds, and Polymarket's about 23. A row read at the start of a crawl was therefore older than the stamp said, by up to that long, while the field's description called it a floor for the whole page.

Now the description is true: no row on the page is older than `observed_at`. The matching endpoint's `snapshot.observed_at` already worked this way, so the two now follow the same rule.

For you, the value is earlier than before by up to about 45 seconds. It was usually minutes old anyway, because the catalog refreshes about every 30 minutes. Nothing else about it changed. It is still `null` when a snapshot carries no time, still the same on every page of one cursor traversal, still the oldest across providers, and still that provider's own value under `?provider=`.

Each provider's snapshot gets its start the next time that provider's crawl finishes after this deploys, so the full catalog is dated by crawl starts within about one crawl cycle. Until a provider has crawled again, its snapshot is dated by when it was published, which is the value it had before. The stamp therefore never becomes `null` because of this change and never moves later; it only moves earlier as providers crawl again.

No parameter, field, type or status code changed, so there is nothing to update in the SDKs. Their generated comments for the field were reworded to say "began reading".