Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

tierwatch: Gemma 4 reads the free-tier pages I depend on, and has to quote every number

Description and use

tierwatch uses Gemma 4 to extract and verify free‑tier API limits, automatically detecting changes and alerting users.

Problem

Freelancers and small agencies rely on free or near‑free API plans that change quietly; when limits shift they only notice after receiving 429 errors.

Outcome

tierwatch automatically detects and reports changes to free‑tier limits, preventing silent failures and enabling proactive adjustments.

Workflow

  • Fetch page or Wayback capture and flatten to plain text
  • Extract structured facts with Gemma 4
  • Verify each fact’s quote and value against the page text
  • Diff facts by key between snapshots
  • Summarise diff against user’s note and output alerts

Evidence

tierwatch keeps a snapshot of each page you list, has an open‑weight model (Gemma 4) pull the limits out as structured facts, throws away every fact whose quoted evidence is not actually on the page, and diffs the facts against the previous snapshot.

Source

The pipeline has five steps: Fetch and flatten… Extract with Gemma 4… Verify in code… Diff by key… Summarise the diff…

Source

The check is also strict enough to throw away correct facts. Brave prints $5 and per 1,000 requests as separate elements. Gemma quoted only the second half, the value wasn’t inside the quote, and the price was dropped.

Source

  • Record date: 2026-10-13T03:41:36.299Z