Why I track every AI quota reset announcement (and why the site has no admin panel)
This month my Codex plan hit 0% for the third time, and each time I found out the reset schedule had quietly moved. I was the kind of person who kept screenshots of the docs in a notes app, but the docs never said when an announced reset actually landed, or which tier was on which clock. So I stopped taking notes and started building a log instead. That log became Alca : a read-only, anonymous,…
For the past three months, my Codex plan has hit 0% quota, and the reset schedule kept shifting without any clear announcement. I used to keep screenshots of the documentation in a notes app, but the documentation never provided exact dates or tiers for the reset. I switched to building a log, which eventually became Alca: an anonymous, read-only website that compares AI model access, pricing, free quotas, and rate limits across different providers.
The reset log, a dated list of reset announcements and limit changes, is the most frequently used feature. Each entry is linked back to the original post. Everything is typed in TypeScript files, with the content editor being a pull request. I edit a file, CI checks ensure referential integrity, and the change is deployed. There is no admin panel, database, or content management system.
I chose this approach to maintain transparency. Verification status tags indicate whether the data comes from a source link (verified) or is a placeholder (unverified). The Codex feed automatically updates every hour from a public API, validating, typechecking, and testing the data before committing changes to the site. Watch entries, which are forecasts, not confirmed events, are marked as unconfirmed.
Feedback is collected through a form that doesn't link to a personal email address. Submissions are checked for size and rate limits before being added to a queue, processed by a heartbeating agent that saves the data durably and acknowledges each submission idempotently. This ensures at-least-once delivery without tracking visitors.
I wonder if providing links back to the original post is useful to anyone other than myself. Do users prefer to cross-check claims against sources or trust the table? I keep the links because a stale limit number once cost me a week of guessing. A dated, cited reset log turns schedule changes from rumors into events. The site can be accessed at https://alca-navy.vercel.app/en/models, and a public JSON API is available under /api/v1 for those who prefer the data over the pages.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
