Direct Wiki Module Data
The main count table is parsed from the SAB Wiki exist modules through the MediaWiki API. The app combines the rarity modules server-side, then shows the module name on each record so the source can be checked.
SAB Exist Count is built to be checkable: it reads public SAB Wiki exist modules, labels estimates clearly, links back to sources, and keeps status/freshness visible instead of asking you to trust a random screenshot.
The main count table is parsed from the SAB Wiki exist modules through the MediaWiki API. The app combines the rarity modules server-side, then shows the module name on each record so the source can be checked.
If the wiki says a count is known, that number is shown as the official exists value. If the wiki says Not Known, estimates are labeled as guesses and never replace the official value.
Data is cached on the server so the site stays fast and does not hammer Fandom when lots of users join during updates or admin abuse. Stale fallback behavior keeps the UI usable if a wiki request is temporarily slow.
The status page tracks wiki modules, parser health, cache freshness, API health, forums, and maintenance mode. If something breaks, the site can show maintenance instead of silently serving broken data.
Brainrot pages include canonical URLs, sitemap entries, source labels, wiki links, images, and history graphs so users and search engines can land on the exact item they need.
Forums and ideas use moderation checks for social links, scams, PII, spam, and unsafe trade wording. The goal is a reference tool first, not a place to move users into sketchy off-site trades.
Trust is better when the receipts are one click away.