Back to browse
Multi-provider iOS usage alerts for AI subscription caps

Multi-provider iOS usage alerts for AI subscription caps

by afonsoduarte·Feb 16, 2026·1 point·1 comment

AI Analysis

●●SolidSolve My ProblemCozy

Glanceable widgets before you hit Claude's 5-hour window. No servers, no signup.

Strengths
  • Multi-provider tracking in one screen solves real daily friction for heavy users
  • On-device architecture with Keychain storage removes trust concerns entirely
  • Native iOS widgets + Lock Screen support makes alerts actually useful, not buried in dashboards
Weaknesses
  • Dashboard-scraping connectors fragile; breaks if provider changes UI
  • iOS-only limits addressability; no Android or web equivalent
Category
Target Audience

Developers using multiple AI services (Claude, ChatGPT, etc.)

Similar To

Dashboards (OpenAI, Anthropic official) · Third-party usage apps (LLM usage trackers)

Post Description

I built AI Usage Tracker, an iOS app that warns you before AI subscription limits cut you off mid-session (e.g. 5-hour windows, weekly caps). I hit this daily while coding: I’d be deep in a session and suddenly hit the cap. Dashboards exist, but they’re not glanceable and there are no practical alerts/widgets. Supports multiple providers in a single screen - Anthropic, OpenAI, MiniMax, Z.ai, Kimi, Codex

Features:

- 5-hour window + weekly status (simple gauges). Makes easy to plan your workload across providers

- reset countdown timers

- Home Screen + Lock Screen widgets

- configurable alerts (e.g. 75%, 90%)

- multi-provider tracking

Privacy / how it works:

- no accounts, no analytics, no servers; everything runs on-device

- API-key providers: paste an API key (stored in iOS Keychain)

- dashboard-only providers: sign in via an embedded web view OR paste an existing session token; the app reads the same usage info shown in the provider dashboard

- connectors may break if dashboards/endpoints change

Not a bypass — it only provides status + alerts so you can plan sessions.

I’d love feedback on:

- which thresholds are actually useful

- % remaining vs time remaining

- security/UX tradeoffs: embedded login vs session-token paste

Similar Projects

Developer Tools●●Solid

Fuelcheck CLI – Monitor token usage across the modern AI providers

It pipes together usage from a long list of providers (Codex, Claude, Gemini, Cursor, Opencode, etc.), offers JSON-first output for automation and a live TUI for human monitoring, and handles multi-account token setups plus local cost scans. Inspired by CodexBar but rewritten in Rust, it feels practical and scriptable — the implementation choices (JSON output, watch mode, provider token_accounts) show attention to real workflows, though the project isn't reinventing the space and some docs/onboarding (e.g., config path naming) could be tightened.

Niche GemSolve My Problem
chungquantin
204mo ago