The latest articles on DEV Community by 410110謝宗恩 (@410110_45616cadd9afa7c). https://dev.to/410110_45616cadd9afa7c https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4131777%2F2a31f44d-87f3-4310-969a-a84e964c47a0.png https://dev.to/410110_45616cadd9afa7c en 410110謝宗恩 Sat, 19 Sep 2026 01:21:44 +0000 https://dev.to/410110_45616cadd9afa7c/why-i-track-every-ai-quota-reset-announcement-and-why-the-site-has-no-admin-panel-1g3i https://dev.to/410110_45616cadd9afa7c/why-i-track-every-ai-quota-reset-announcement-and-why-the-site-has-no-admin-panel-1g3i <p>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 <em>announced</em> reset actually landed, or which tier was on which clock. So I stopped taking notes and started building a log instead.</p> <p>That log became <a href="https://alca-navy.vercel.app/en/models" rel="noopener noreferrer">Alca</a>: a read-only, anonymous, no-signup site comparing AI model access, pricing, free quotas and rate limits across providers. The part I use most is the reset log: a dated list of every announced reset and limit change, each entry linked back to the original post.</p> <h2> The unglamorous part </h2> <p>All the content is typed TypeScript files in a repo: <code>models.ts</code>, <code>offers.ts</code>, <code>codexResets.ts</code>. A "content editor" is just a pull request. I edit a file, CI checks referential integrity (an offer can't reference a model slug that doesn't exist, every URL must be http/https, slugs are unique), and the change deploys. No admin panel, no database for public data, no CMS.</p> <p>I chose that on purpose. When a row says some provider's free tier gets you X requests a day, I want to be able to point at exactly where that came from. Every row carries a <code>verification_status</code>: <code>verified</code> means I checked a source link, and I paste it in. <code>unverified</code> means "this is a placeholder, replace me." Showing the honesty level of the data beats hiding it behind a clean table.</p> <h2> The Codex feed runs itself </h2> <p>The reset feed regenerates about hourly from a public API: fetch, validate, typecheck and test, commit only when the data actually changed, push, and the deploy happens. The upstream blocks datacenter IPs, so it runs on a consumer machine, with a manual workflow as the backup. "Watch" entries — forecasts, not confirmed events — are clearly marked <code>unconfirmed</code>.</p> <h2> Feedback that doesn't land in my inbox </h2> <p>The site has a feedback form, but I didn't want it pointing at a personal email address. Submissions pass size and rate checks, then sit in a queue that an outbound-only agent I run pulls from: it heartbeats, leases up to 20 items, saves them durably, and acks idempotently. Expired leases get redelivered. In practice: at-least-once delivery, no browser-visible tracking of visitors.</p> <h2> What I'm not sure about </h2> <p>Is "linked back to the original post" actually useful to anyone besides me? Do you cross-check a claim against its source, or just trust the table? I keep the links because a stale limit number cost me a week of guessing once. A dated, cited reset log turns a schedule change from a rumor into an event.</p> <p>The site is at <a href="https://alca-navy.vercel.app/en/models" rel="noopener noreferrer">https://alca-navy.vercel.app/en/models</a>. There's a feedback form, and a public JSON API under <code>/api/v1</code> if you want the data instead of the pages.</p> webdev sideprojects ai coding