Methodology

Methodology

How the daily snapshot is collected, how each metric is defined, and where the limits are.

Pipeline

  1. A collection script pulls public feeds once a day: Steam's charts and store APIs, Hugging Face's model API, benchmark snapshots published by third parties, Liquipedia's tournament page and RSS news feeds.
  2. Raw responses are stored as a dated snapshot and written to a local database.
  3. The site is generated from that snapshot: leaderboard pages, one page per tracked entity, a daily brief and open data exports.
  4. Numbers in the generated pages come from the snapshot; the build fails rather than inventing a missing value.

Definitions

Update cadence

The snapshot is collected daily; this build used the November 7, 2026 snapshot. Benchmark boards update less often, so each board shows its own "as of" date. Entity history starts with the first stored snapshot — there is no backfill, and the site says so on pages without history.

Known limitations

AI crawlers and reuse

The site is server-rendered HTML. Crawlers for search and AI answers — including GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot and Bingbot — are allowed in robots.txt. Google-Extended is also allowed so the content can be used for Gemini grounding; AI Overviews use regular Googlebot and cannot be opted out of separately.

The JSON and CSV exports are free to reuse with attribution to the page and the original source. See open data.

Corrections

If a figure is wrong, send the page URL, the correct value and a source link via the contact page. Corrections are applied to the next daily build.