Skip to main content
A self-contained script that lists the indices your token holds, reads the latest value of one, pages two years of its history, and overlays the daily series on the 30-minute series for the same GPU — the standard pattern for reading a benchmark at two resolutions. It is also the shortest complete demonstration of the two things that differ from v1: following meta.next to page through results, and date ranges that exclude the end date.

What this does

  1. Discover — reads /metadata for the ids the token holds and each one’s row_type.
  2. Latest — reads the current value of the daily H100 index, a single row.
  3. History — pages the full two-year series, following meta.next to exhaustion.
  4. Intraday — pulls the last week of the 30-minute series for the same GPU.
  5. Overlay — lines up the daily level with the last intraday level of each day.
All index values are in $/GPU-hr. Every row has id, type, timestamp, value, p5 and p95. A daily row’s timestamp is a calendar date; an intraday row’s is a UTC instant — a response never mixes the two, because a request names one index. Treat p5 and p95 as optional: points from General Index (meta.source is gx) carry the level only, so those two come back null. Set source to choose — see Choosing a source.
walk() above passes params on the first request only, then follows meta.next.url as given. Passing them again returns a 400 — the link already carries them.

Customizing

  • Another index — swap the id. Family-level daily indices are rental-hopper-1y-us-daily and rental-blackwell-1y-us-daily; GPU-level ones name the GPU, and each has an …-intraday counterpart. /metadata lists exactly what your token holds.
  • Point-in-time — swap /history for /as-of?at=2026-06-01 to ask what the index read on a given day. A non-publication day carries back to the prior published value.
  • Ordering — sort_by=value&sort_order=desc gives the highest levels first; the default is oldest first by timestamp.