# Catalog ingestion and API documentation hardening (https://docs.predictorsdk.com/changelog/2026-08-31-enterprise-api-hardening)

2026-08-31 · Fix, Infra, SDK

Kalshi's full catalog now streams into an unpublished Redis snapshot one page
at a time and publishes atomically only after the crawl completes. This removes
the multi-million-row in-memory copies that caused a production jobs worker to
be OOM-killed while preserving the previous good snapshot on any interruption.
Publication now verifies every construction key's marker, TTL, and exact
cardinality under a Redis watch, so storage pressure rejects an evicted build
instead of activating partial data. Valkey capacity was raised to hold the
active catalog and its largest complete replacement at the same time.
An independent scheduled live check now fails when any provider's published
catalog snapshot is older than the configured freshness bound.

Sports matching now refuses AlphaArcade rows whose structured game date
contradicts an explicit date in the source's title or slug. Those rows remain
available in the provider-native catalog; only the unsupported identity claim
is withheld.

The SDK guides now document the `provider` catalog filter, the `snapshot`
freshness block, and typed `409 Conflict` errors. Identifier descriptions and
matching guidance were corrected, the landing example was refreshed from one
coherent four-provider event, and the canonical OpenAPI YAML is available at
[`/openapi.yaml`](https://docs.predictorsdk.com/openapi.yaml) with a byte-for-byte CI check against the
source spec.