Data freshness

Every surface Polyrank serves is stamped with the exact chain block (or observation time) it reflects, in one registry. You never have to memorize per-widget staleness folklore: ask the endpoint, or read the X-Data-As-Of-Block / X-Data-As-Of-Time response headers on the leaderboard, trader, and market rails.

GET /v1/meta/freshness

Anonymous — no API key needed.

curl -s https://api.polyrank.app/v1/meta/freshness | jq '.surfaces[] | {surface, status, as_of_block, age_seconds}'

{
  "surfaces": [
    {
      "surface": "pnl.realized",
      "anchor": "block",
      "label": "Realized P&L (per-wallet)",
      "status": "measured",
      "as_of_block": "75123456",
      "as_of_time": "2026-08-31T12:00:00.000Z",
      "age_seconds": 93,
      "budget_seconds": 18000
    }
  ],
  "frontier_readable": true,
  "as_of": "2026-08-31T12:01:33.000Z"
}

The four anchor classes

Not everything can be block-aligned, and pretending otherwise would be its own confusion:

• block — truth lives on-chain (trades, P&L, positions, resolutions). as_of_block is the exact Polygon block the surface reflects.
• time — observations that exist only at the moment of capture (CLOB midpoints, market metadata). A mid has no block; a missed observation is gone, not "behind".
• slot — the prediction ledger's pre-registered 15-minute slots (a design property, not a staleness bug).
• cohort — ranks and percentiles are anchored to the vintage of the inputs they ranked: input_frontier carries the block of the metric snapshot that was ranked. Recomputing a rank per block is neither possible nor meaningful.

A registered surface with no stamp yet is status: "unmeasured" — absence never means fresh.

The registry